CVE-2026-42043: Axios: 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
Noroxi assessment
Priority: Plan (action score 40/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.71% (FIRST EPSS); higher than 54.1% of all records.
- 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 1.15.1.
- Severity is disputed: the assigning authority (CNA) scores it 7.2, NVD 10.0.
Add it to your regular patch cycle. Upgrade to axios axios 1.15.1 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. Prior to 1.15.1 and 0.31.1, an attacker who can influence the target URL of an Axios request can use any address in the 127.0.0.0/8 range (other than 127.0.0.1) to completely bypass the NO_PROXY protection. This vulnerability is due to an incomplete for CVE-2025-62718, This vulnerability is fixed in 1.15.1 and 0.31.1.
- Published
- Apr 24, 2026
- Updated
- Nov 11, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-183
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 10.0
- CNA · GitHub_M
- 7.2
- 2.8 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A: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.
Is the Axios on your site affected?Scan JavaScript libraries
Is your version affected? Check itNoroxi 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 librariesVersions 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.15.1, < 0.31.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- axios axiosbefore 0.31.1
- axios axios1.0.0 and later · before 1.15.1
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.15.2-1 | 1.15.2-1 |
| npm | axios | from 1.0.0 · before 1.15.1 | 1.15.1 |
| npm | axios | before 0.31.1 | 0.31.1 |
Same product
axios: all recordsOther highest-scoring records for the same primary product.
- 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…39Monitor
- CVE-2026-44492Axios: shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)38Monitor
- CVE-2026-42264Axios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-42041Apr 24, 2026 · Axios: Authentication Bypass via Prototype Pollution Gadget in `validateStatus` Merge Strategy26Monitor
- ← EarlierCVE-2026-42042Apr 24, 2026 · Axios: XSRF Token Cross-Origin Leakage via Prototype Pollution Gadget in `withXSRFToken` Boolean Coercion21Monitor
- Later →CVE-2026-42044Apr 24, 2026 · Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget in `parseReviver`36Monitor
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 | 1.15.1 · description | Vendor (CNA) |
| debian:node-axios | 1.15.2-1 · Debian:14 | Package registry (OSV) |
| npm:axios | 0.31.1 | Package registry (OSV) |
| npm:axios | 1.15.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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6731599 days apartaxios 0.31.0 before 0.33.0 and 1.15.0 before 1.18.0 NO_PROXY Bypass via 0.0.0.027Monitor
- CVE-2026-420420 days apartAxios: XSRF Token Cross-Origin Leakage via Prototype Pollution Gadget in `withXSRFToken` Boolean Coercion21Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-183 · Permissive List of Allowed InputsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
nvd-primary
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)
- Double EncodingCAPEC-120likelihood: Low · Medium
- Using Leading 'Ghost' Character Sequences to Bypass Input FiltersCAPEC-3likelihood: Medium · Medium
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Using Unicode Encoding to Bypass Validation LogicCAPEC-71likelihood: Medium · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:16476
- access.redhat.com/errata/RHSA-2026:16532
- access.redhat.com/errata/RHSA-2026:16534
- access.redhat.com/errata/RHSA-2026:16535
- access.redhat.com/errata/RHSA-2026:16542
- access.redhat.com/errata/RHSA-2026:16874
- access.redhat.com/errata/RHSA-2026:17468
- access.redhat.com/errata/RHSA-2026:17474
- access.redhat.com/errata/RHSA-2026:17657
- access.redhat.com/errata/RHSA-2026:17699
- access.redhat.com/errata/RHSA-2026:19109
- access.redhat.com/errata/RHSA-2026:19375
- access.redhat.com/errata/RHSA-2026:20889
- access.redhat.com/errata/RHSA-2026:20938
- access.redhat.com/errata/RHSA-2026:21017
- access.redhat.com/errata/RHSA-2026:21338
- access.redhat.com/errata/RHSA-2026:21772
- access.redhat.com/errata/RHSA-2026:22465
- access.redhat.com/errata/RHSA-2026:22619
Vendor advisories and official records. Exploit/PoC links are deliberately left out.