CVE-2026-67318: axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2

Published Aug 1, 2026
·
Updated

axios versions =1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.

Other sources

axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.

— MITRE

Affected Software

3 affected components
npm/axios>=1.13.0<1.18.0
Axios Axios Node.js>=1.13.0<1.18.0
IBM Aspera Enterprise WebApps<=1.0.0 - 1.0.5

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.

    Patch axios 1.13.0 before 1.18.0 maxBodyLength Bypass via HTTP/2

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
DescriptionSeverityWeaknessAffected Software
Sep 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-67318?

CVE-2026-67318 has a risk rating of 19.

2

How do I fix CVE-2026-67318?

To mitigate CVE-2026-67318, update axios to version 1.18.0 or later.

3

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

CVE-2026-67318 affects axios versions 1.13.0 through 1.17.0.

4

What exploit does CVE-2026-67318 allow?

CVE-2026-67318 allows a maxBodyLength bypass when using HTTP/2 in axios.

5

What component is primarily affected by CVE-2026-67318?

The Node.js HTTP adapter in axios is primarily affected by CVE-2026-67318.

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