CVE-2023-45857: An issue discovered in Axios 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-
Noroxi assessment
Priority: Monitor (action score 26/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.70% (FIRST EPSS); higher than 53.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: node-axios (Debian:12) 1.2.1+dfsg-1+deb12u1; node-axios (Debian:13) 1.6.2+dfsg-1; axios (npm) 0.28.0, 1.6.0.
Low priority for now. Upgrade to node-axios (Debian:12) 1.2.1+dfsg-1+deb12u1; node-axios (Debian:13) 1.6.2+dfsg-1; axios (npm) 0.28.0, 1.6.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
An issue discovered in Axios 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
- Published
- Nov 8, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-352
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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 axios1.5.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 | before 1.2.1+dfsg-1+deb12u1 | 1.2.1+dfsg-1+deb12u1 |
| Debian:13 | node-axios | before 1.6.2+dfsg-1 | 1.6.2+dfsg-1 |
| npm | axios | from 0.8.1 · before 0.28.0 | 0.28.0 |
| npm | axios | from 1.0.0 · before 1.6.0 | 1.6.0 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.5-1.el8ap | 0:1.4.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.5-1.el8ap | 0:1.4.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | receptor | before 0:1.4.5-1.el9ap | 0:1.4.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | receptorctl | before 0:1.4.5-1.el9ap | 0:1.4.5-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-venv-tower | before 0:4.5.5-2.el8ap | 0:4.5.5-2.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-aiohttp | before 0:3.9.3-1.el8ap | 0:3.9.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-aiohttp-debuginfo | before 0:3.9.3-1.el8ap | 0:3.9.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python39-django | before 0:4.2.11-1.el8ap | 0:4.2.11-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-aiohttp | before 0:3.9.3-1.el8ap | 0:3.9.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-aiohttp-debugsource | before 0:3.9.3-1.el8ap | 0:3.9.3-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el8 | python3x-django | before 0:4.2.11-1.el8ap | 0:4.2.11-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-venv-tower | before 0:4.5.5-2.el9ap | 0:4.5.5-2.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-aiohttp | before 0:3.9.3-1.el9ap | 0:3.9.3-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-aiohttp-debugsource | before 0:3.9.3-1.el9ap | 0:3.9.3-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python-django | before 0:4.2.11-1.el9ap | 0:4.2.11-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python3-aiohttp | before 0:3.9.3-1.el9ap | 0:3.9.3-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python3-aiohttp-debuginfo | before 0:3.9.3-1.el9ap | 0:3.9.3-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el9 | python3-django | before 0:4.2.11-1.el9ap | 0:4.2.11-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-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-2020-28168Nov 6, 2020 · Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providin24Monitor
- ← EarlierCVE-2021-3749Aug 31, 2021 · Inefficient Regular Expression Complexity in axios/axios33Monitor
- Later →CVE-2024-39338Aug 12, 2024 · axios 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs.30Monitor
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 |
|---|---|---|
| debian:node-axios | 1.2.1+dfsg-1+deb12u1 · Debian:12 | Package registry (OSV) |
| npm:axios | 0.28.0 | Package registry (OSV) |
| npm:axios | 1.6.0 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.5-2.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-aiohttp | 0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python-aiohttp-debugsource | 0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-aiohttp | 0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python3-aiohttp-debuginfo | 0:3.9.3-1.el9ap · Red Hat:ansible_automation_platform:2.4::el9 | Package registry (OSV) |
| red hat:python39-aiohttp | 0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-aiohttp-debuginfo | 0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python39-django | 0:4.2.11-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-aiohttp | 0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-aiohttp-debugsource | 0:3.9.3-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2023-10-18 |
| Proof-of-concept repository on GitHub | stars:0 | 2023-10-26 |
| Proof-of-concept repository on GitHub | stars:1 | 2023-11-24 |
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.
- First PoC-22 d
- Published
- TodayOct 31, 2026+1088 d
No history yet (it accumulates with the daily EPSS job).
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.
No nightly-computed relations.
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.
- A user must open a link or visit a page.
- 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
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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.