⚠ Withdrawn by GitHub Security Advisories

Withdrawn: September 1, 2026

GHSA-fqj3-h9pc-443hMediumCVSS 5.3Disclosed before NVD

Duplicate Advisory: Axios: HTTP/2 streamed uploads bypass `maxBodyLength`

Published
August 1, 2026
Last Modified
September 1, 2026

📋 Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-mwf2-3pr3-8698. This link is maintained to preserve external references.

Original Description

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.

🎯 Affected products1

  • npm/axios:>= 1.13.0, < 1.18.0

🔗 References (4)