CVE-2026-67319: axios before 0.33.0 Prototype Pollution via nested option objects
Noroxi assessment
Priority: Monitor (action score 25/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.31% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: axios axios 0.33.0, 1.18.0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to axios axios 0.33.0, 1.18.0 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 before 0.33.0 (and 1.x before 1.18.0) can consume inherited properties from nested request option objects when the JavaScript process's Object.prototype has already been polluted by another component. While the top-level merged config uses a null prototype, nested plain objects such as auth and paramsSerializer are cloned into ordinary objects and read without own-property checks. When an application passes placeholder nested objects such as auth: {} or paramsSerializer: {}, inherited username/password values can cause silent injection of an Authorization: Basic header, and inherited encode/serialize values can alter query-string serialization (full serializer replacement requires a function-valued pollution primitive). This is exploitable only in the presence of pre-existing prototype pollution.
- Published
- Aug 1, 2026
- Updated
- Sep 1, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- CWE-1321
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 6.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/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
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| axios | axios | cpe:2.3:a:axios:axios |
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 librariesAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- axios axiosbefore 0.33.0
- axios axios1.0.0 and later · before 1.18.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
axios axios
- 0.33.0, 1.18.0not affected
- 0.8.0 and later · before 0.33.0affected · semver
- 1.0.0 and later · before 1.18.0affected · semver
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.18.0-1 | 1.18.0-1 |
| npm | axios | from 0.8.0 · before 0.33.0 | 0.33.0 |
| npm | axios | from 1.0.0 · before 1.18.0 | 1.18.0 |
| openSUSE:Tumbleweed | agama-web-ui | before 24+0.a836cced5-52.1 | 24+0.a836cced5-52.1 |
| Red Hat:hummingbird:1 | grafana12.4 | before 0:12.4.6-0.3.hum1 | 0:12.4.6-0.3.hum1 |
| Red Hat:hummingbird:1 | grafana13.1 | before 0:13.1.1-0.4.hum1 | 0:13.1.1-0.4.hum1 |
Same product
axios: all recordsOther 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.040Plan
- 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 s39Monitor
- CVE-2026-44492Axios: shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)38Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-67317Aug 1, 2026 · axios 1.7.0 before 1.18.0 maxBodyLength Bypass via ReadableStream25Monitor
- ← EarlierCVE-2026-67318Aug 1, 2026 · axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/225Monitor
- Later →CVE-2026-67320Aug 1, 2026 · axios before 0.33.0 Prototype Pollution via Node HTTP adapter33Monitor
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.33.0 | Vendor (CNA) |
| axios axios | 1.18.0 | Vendor (CNA) |
| debian:node-axios | 1.18.0-1 · Debian:14 | Package registry (OSV) |
| npm:axios | 0.33.0 | Package registry (OSV) |
| npm:axios | 1.18.0 | Package registry (OSV) |
| opensuse:agama-web-ui | 24+0.a836cced5-52.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:grafana12.4 | 0:12.4.6-0.3.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:grafana13.1 | 0:13.1.1-0.4.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.
No dated events beyond publication.
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.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- asadeddinreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-4226485 days apartAxios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking36Monitor
- CVE-2026-10190958 days apartAxios: Prototype Pollution Gadget in axios toFormData Options33Monitor
- CVE-2026-4449051 days apartAxios: DoS & Header Injection via Prototype Pollution Read-Side Gadgets in axios merge functions32Monitor
- CVE-2026-4203399 days apartAxios: Prototype Pollution Gadgets - Response Tampering, Data Exfiltration, and Request Hijacking29Monitor
- CVE-2026-10190258 days apartAxios: Prototype-Pollution Gadget in the Default Instance Allows Inherited Object.prototype.method to Override HTTP Method27Monitor
- CVE-2026-10190858 days apartAxios: Prototype pollution gadget in fetch adapter can alter outbound requests27Monitor
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-0718 · Aug 3, 2026(Axios HTTP Client Güvenlik Bildirimi)
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- 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:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/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
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.