CyberRota Analysis
AI-GeneratedAxios versions 1.13.0 and later are vulnerable when handling streamed request bodies over HTTP/2, as they fail to enforce the configured maxBodyLength limit. This can lead to excessive resource consumption and policy bypass, potentially impacting service availability and upstream quotas, but does not allow for code execution or credential disclosure. Organizations using affected versions of Axios in environments that utilize HTTP/2 should prioritize addressing this vulnerability to mitigate potential resource exhaustion risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.