CVE-2026-67316: axios before 1.18.0 Prototype Pollution via bodyless methods

Published Aug 1, 2026
·
Updated

axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.

Affected Software

1 affected component
npm/axios<1.18.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade axios to a version that resolves this vulnerability.

    Fixed in 1.18.0
  2. Upgrade

    Upgrade axios to a version that resolves this vulnerability.

    Fixed in 0.33.0

Event History

Aug 1, 2026
CVE Published
via MITRE·12:22 PM
Data Sourced
via MITRE·12:22 PM
DescriptionWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-67316?

CVE-2026-67316 has a risk score of 37, indicating a moderate level of vulnerability.

2

How do I fix CVE-2026-67316?

To fix CVE-2026-67316, upgrade axios to version 1.18.0 or later.

3

What causes CVE-2026-67316?

CVE-2026-67316 is caused by prototype pollution via bodyless methods in axios that can manipulate request construction.

4

Which versions of axios are affected by CVE-2026-67316?

All versions of axios prior to 1.18.0 are affected by CVE-2026-67316.

5

Can CVE-2026-67316 lead to a security breach?

Yes, CVE-2026-67316 can potentially lead to security breaches if exploited by modifying the prototype of objects used in requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203