CVE-2026-101902· NVD / CVE Program· CNA GitHub_M

Axios: Prototype-Pollution Gadget in the Default Instance Allows Inherited Object.prototype.method to Override HTTP Method

Noroxi assessment

Priority: Monitor (action score 27/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: axios axios 0.34.0; azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0 Release Notes.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to axios axios 0.34.0; azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Axios is a promise-based HTTP client for the browser and Node.js. From 0.27.2 until 0.34.0 and 1.20.0, Axios default-instance requests that omit an explicit method can read an inherited method value from Object.prototype. If another vulnerability in the same process pollutes Object.prototype.method, calls such as axios.request({ url }) and axios({ url }) can send a state-changing HTTP method instead of the expected default GET. Axios does not create the prototype pollution source. This is a read-side gadget in axios request dispatch. This issue is fixed in version 0.34.0 and 1.20.0.

MediumCVSS 6.9 · v4.0—No exploit Fix available

Published: Sep 28, 2026
Updated: Sep 30, 2026
EPSS: 0.4% · 34th percentile
CWE: CWE-1321

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.9 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: proof of concept
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.9; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Is the Axios on your site affected?

The free JavaScript library scanner reads the Axios version from the files your site loads, matches this record and other known vulnerabilities, and gives the safe version on the same branch. If the version can't be read, it says so. No account needed.

Scan JavaScript libraries

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

axios axios
- >= 1.0.0, < 1.20.0, >= 0.27.2, < 0.34.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	node-axios	from 0	—
Debian:14	node-axios	before 1.20.0-1	1.20.0-1
npm	axios	from 0.27.2 · before 0.34.0	0.34.0
npm	axios	from 1.0.0 · before 1.20.0	1.20.0
Red Hat:hummingbird:1	grafana12.4	before 0:12.4.12-0.3.hum1	0:12.4.12-0.3.hum1
Red Hat:hummingbird:1	grafana13.1	before 0:13.1.6-0.6.hum1	0:13.1.6-0.6.hum1
Red Hat:hummingbird:1	grafana13.2	before 0:13.2.1-0.9.hum1	0:13.2.1-0.9.hum1

Same product

axios: all records

Other highest-scoring records for the same primary product.

CVE-2026-42043Axios: Incomplete Fix for CVE-2025-62718 — NO_PROXY Protection Bypassed via RFC 1122 Loopback Subnet (127.0.0.0/8) in Axios 1.15.0
40Plan
CVE-2024-57965In axios before 1.7.8, lib/helpers/isURLSameOrigin.js does not use a URL object when determining an origin, and has a potentially unwanted s
39Monitor
CVE-2026-42264Axios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-101900Sep 28, 2026 · Axios: Fetch Adapter Header Injection via Inherited FormData getHeaders
27Monitor
← EarlierCVE-2026-101901Sep 28, 2026 · Axios: Denial of Service via Unhandled 'error' Event in HTTP/2 ClientHttp2Session Initialization
32Monitor
Later →CVE-2026-101903Sep 28, 2026 · Axios: ReDoS in fromDataURI data: URL parser freezes the Node event loop (DoS)
32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
axios axios	0.34.0 · description	Vendor (CNA)
azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
debian:node-axios	1.20.0-1 · Debian:14	Package registry (OSV)
npm:axios	0.34.0	Package registry (OSV)
npm:axios	1.20.0	Package registry (OSV)
red hat:grafana12.4	0:12.4.12-0.3.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:grafana13.1	0:13.1.6-0.6.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:grafana13.2	0:13.2.1-0.9.hum1 · Red Hat:hummingbird:1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedSep 28, 2026
Fix recordedSep 28, 2026same day
TodayOct 19, 2026+21 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-42264143 days apartAxios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking
36Monitor
CVE-2026-1019090 days apartAxios: Prototype Pollution Gadget in axios toFormData Options
33Monitor
CVE-2026-44490109 days apartAxios: DoS & Header Injection via Prototype Pollution Read-Side Gadgets in axios merge functions
32Monitor
CVE-2026-42033157 days apartAxios: Prototype Pollution Gadgets - Response Tampering, Data Exfiltration, and Request Hijacking
29Monitor
CVE-2026-1019080 days apartAxios: Prototype pollution gadget in fetch adapter can alter outbound requests
27Monitor
CVE-2026-6731958 days apartaxios before 0.33.0 Prototype Pollution via nested option objects
25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1204 · Sep 29, 2026(Axios HTTP Client Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010

Change log

Fix✗ → ✓Sep 28, 2026, 11:20 PM UTC
SSVC exploitation— → pocSep 28, 2026, 8:49 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/axios/axios/commit/d19040bda7a8be2f82c3c6e1a5bc03917daee39a

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records