dbcve.org
AxiosApplication

CVE-2026-42264

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 1.15.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Axios is a promise based HTTP client for the browser and Node.js. From version 1.0.0 to before version 1.15.2, fFive config properties (auth, baseURL, socketPath, beforeRedirect, and insecureHTTPParser) in the HTTP adapter are read via direct property access without hasOwnProperty guards, making them exploitable as prototype pollution gadgets. When Object.prototype is polluted by another dependency in the same process, axios silently picks up these polluted values on every outbound HTTP request. This issue has been patched in version 1.15.2.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 2mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Axios HTTP client versions 1.0.0 to before 1.15.2 read five config properties (auth, baseURL, socketPath, beforeRedirect, insecureHTTPParser) via direct property access without hasOwnProperty guards, enabling prototype pollution gadgets exploitable when Object.prototype is polluted by another dependency in the same process.

MitigationUpgrade Axios to version 1.15.2 or later which adds hasOwnProperty guards to prevent prototype pollution via config properties.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AxiosApplication
Affected:>= 1.0.0, < 1.15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Axios version
    Run 'npm list axios' or inspect your package.json dependencies to find the axios version number
    Affected if The version is 1.0.0 through 1.15.1 (any version before 1.15.2)
  2. Audit dependencies for prototype pollution risks
    Review all direct and transitive dependencies in package.json, looking for packages known to have prototype pollution vulnerabilities or that perform untrusted object property assignment
    Affected if Any dependency in the project has or could introduce prototype pollution behavior
  3. Identify axios config usage
    Search your codebase for axios request calls that use config objects containing 'auth', 'baseURL', 'socketPath', 'beforeRedirect', or 'insecureHTTPParser' properties
    Affected if These specific config properties are used in axios requests while running with a polluted Object.prototype

You are affected if your installed axios version is between 1.0.0 and 1.15.1 AND another dependency in your project pollutes Object.prototype AND you use the five vulnerable config properties in axios requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.15.2 or later
Fixed in 1.15.2
Vendor patch github.com →
Interim mitigation

Upgrade Axios to version 1.15.2 or later which adds hasOwnProperty guards to prevent prototype pollution via config properties.

Recommended fix High confidence

1.15.2

  1. Upgrade axios to version 1.15.2 or later by running: npm install [email protected] (or yarn add [email protected])
  2. After upgrading, verify that your application functions correctly with the new axios version
  3. If using a package-lock.json or yarn.lock file, ensure it is regenerated with the new version
Caveat Minimal expected; 1.15.2 is a patch release focused on security fix within the 1.x line

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Axios Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42264 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42264 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data