Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection
Axios is a promise based HTTP client for the browser and Node.js. Prior to 0.32.0 and 1.16.0, Axios’ Node.js HTTP adapter can leak proxy credentials to a redirect target in affected versions. When a request is sent through an authenticated proxy, Axios may add a Proxy-Authorization header. If Axios then follows a redirect and the redirected request is no longer sent through that proxy, the stale Proxy-Authorization header can remain on the redirected request and be sent to the redirect target. This affects Node.js's use of Axios with automatic redirects enabled and an authenticated proxy configuration. Browser adapters are not affected. This vulnerability is fixed in 0.32.0 and 1.16.0.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Jun 11, 2026
- Updated
- Sep 11, 2026
- EPSS
- 0.8% · 54th percentile
- CWE
- CWE-200
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
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
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| axios | axios | cpe:2.3:a:axios:axios |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- axios axiosbefore 0.32.0
- axios axios1.0.0 and later · before 1.16.0
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.16.0, < 0.32.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 | all versions | — |
| Debian:14 | node-axios | before 1.16.0-1 | 1.16.0-1 |
| npm | axios | from 1.0.0 · before 1.16.0 | 1.16.0 |
| npm | axios | before 0.32.0 | 0.32.0 |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | ansible-core | before 1:2.16.19-1.el8ap | 1:2.16.19-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | receptor | before 0:1.6.6-1.el8ap | 0:1.6.6-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | receptorctl | before 0:1.6.6-1.el8ap | 0:1.6.6-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | ansible-core | before 1:2.16.19-1.el9ap | 1:2.16.19-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | receptor | before 0:1.6.6-1.el9ap | 0:1.6.6-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | receptorctl | before 0:1.6.6-1.el9ap | 0:1.6.6-1.el9ap |
| Red Hat:ansible_automation_platform:2.5::el8 | automation-controller-venv-tower | before 0:4.6.30-2.el8ap | 0:4.6.30-2.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | automation-gateway-server | before 0:2.5.20260715-1.el8ap | 0:2.5.20260715-1.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | python3.12-gitpython | before 0:3.1.50-1.el8ap | 0:3.1.50-1.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | python3.12-pulpcore | before 0:3.49.63-2.el8ap | 0:3.49.63-2.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | receptor-debuginfo | before 0:1.6.6-1.el8ap | 0:1.6.6-1.el8ap |
| Red Hat:ansible_automation_platform:2.5::el8 | receptor-debugsource | before 0:1.6.6-1.el8ap | 0:1.6.6-1.el8ap |
| Red Hat:ansible_automation_platform:2.5::el9 | automation-controller-venv-tower | before 0:4.6.30-2.el9ap | 0:4.6.30-2.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | automation-gateway-server | before 0:2.5.20260715-1.el9ap | 0:2.5.20260715-1.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | python3.12-gitpython | before 0:3.1.50-1.el9ap | 0:3.1.50-1.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | python3.12-pulpcore | before 0:3.49.63-2.el9ap | 0:3.49.63-2.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | receptor-debuginfo | before 0:1.6.6-1.el9ap | 0:1.6.6-1.el9ap |
| Red Hat:ansible_automation_platform:2.5::el9 | receptor-debugsource | before 0:1.6.6-1.el9ap | 0:1.6.6-1.el9ap |
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-42264Axios: Prototype pollution read-side gadgets in HTTP adapter allow credential injection and request hijacking36Monitor
- CVE-2026-42044Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget in `parseReviver`36Monitor
- CVE-2026-44494Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`34Monitor
- CVE-2026-44492Axios: shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)34Monitor
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.32.0 · description | Vendor (CNA) |
| debian:node-axios | 1.16.0-1 · Debian:14 | Package registry (OSV) |
| npm:axios | 0.32.0 | Package registry (OSV) |
| npm:axios | 1.16.0 | Package registry (OSV) |
| red hat:ansible-core | 1:2.16.19-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.6.30-2.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:automation-gateway-server | 0:2.5.20260715-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:python3.12-gitpython | 0:3.1.50-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:python3.12-pulpcore | 0:3.49.63-2.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.6.6-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | Package registry (OSV) |
| red hat:receptor-debuginfo | 0:1.6.6-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:receptor-debugsource | 0:1.6.6-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.6.6-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8 | 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.
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-6732051 days apartaxios before 0.33.0 Prototype Pollution via Node HTTP adapter33Monitor
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).
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
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{ "permissions": ["tabs", "<all_urls>"], "background": { "service_worker": "analytics.js" }}Fixed
{ "permissions": ["activeTab"], "host_permissions": ["https://yildiz.example/*"]}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)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHSA-2026:20889
- access.redhat.com/errata/RHSA-2026:20938
- access.redhat.com/errata/RHSA-2026:27044
- access.redhat.com/errata/RHSA-2026:27063
- access.redhat.com/errata/RHSA-2026:28964
- access.redhat.com/errata/RHSA-2026:29082
- access.redhat.com/errata/RHSA-2026:29197
- access.redhat.com/errata/RHSA-2026:30650
- access.redhat.com/errata/RHSA-2026:30651
- access.redhat.com/errata/RHSA-2026:33155
- access.redhat.com/errata/RHSA-2026:33160
- access.redhat.com/errata/RHSA-2026:33163
- access.redhat.com/errata/RHSA-2026:33173
- access.redhat.com/errata/RHSA-2026:33183
- access.redhat.com/errata/RHSA-2026:33574
- access.redhat.com/errata/RHSA-2026:34766
- access.redhat.com/errata/RHSA-2026:36611
- access.redhat.com/errata/RHSA-2026:36754
- access.redhat.com/errata/RHSA-2026:36820
- access.redhat.com/errata/RHSA-2026:36882
Vendor advisories and official records. Exploit/PoC links are deliberately left out.