EUVD-2026-51826
GHSA-fqj3-h9pc-443h
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
AC:H reflects the specific conjunction of HTTP/2 transport, stream body type, finite maxBodyLength, and attacker-controlled stream required; no confidentiality or integrity impact applies.
AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4Blast Radius
ecosystem impact- 25 npm packages depend on axios (15 direct, 10 indirect)
Ecosystem-wide dependent count for version 1.13.0.
DescriptionCVE.org
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.
AnalysisAI
HTTP/2 streamed upload requests in axios 1.13.0-1.17.x bypass the configured maxBodyLength limit, allowing applications that proxy attacker-controlled streams to an upstream HTTP/2 service to transmit outbound data of arbitrary size. The flaw is constrained to upload-forwarding architectures that explicitly configure a finite maxBodyLength, use the Node.js HTTP adapter with httpVersion: 2, and accept streamed request bodies - conditions common in reverse-proxy and file-upload relay patterns. Impact is limited to resource exhaustion and policy bypass (excess egress costs, upstream quota consumption, limited availability); no public exploit has been identified and the CVE is not listed in CISA KEV.
Technical ContextAI
axios is a promise-based HTTP client for Node.js and browsers, distributed via npm (CPE: cpe:2.3:a:axios:axios:*:*:*:*:*:*:*:*). In its Node.js adapter (lib/adapters/http.js), when the request option httpVersion resolves to '2', axios routes through Node's native http2Transport rather than the follow-redirects-backed HTTP/1.1 path. The root cause (CWE-400: Uncontrolled Resource Consumption) is a logic gap between transport selection and enforcement: axios writes config.maxBodyLength to the options object, but Node's HTTP/2 request API silently ignores that field. The stream-level byte-counting wrapper that would otherwise enforce the limit is conditioned on config.maxBodyLength > -1 && config.maxRedirects === 0; because HTTP/2 calls bypass follow-redirects and default maxRedirects is non-zero, this wrapper is never entered, and uploadStream.pipe(req) forwards the full stream to the upstream service uncapped. String, Buffer, and ArrayBuffer bodies are pre-validated before transport selection and remain unaffected. The affected npm package range is >=1.13.0 <1.18.0.
RemediationAI
Upgrade axios to version 1.18.0, which contains the upstream fix via commit 32fc489632377d214db55bfa4e2c48486a7d7ce2 (PR #11000 at https://github.com/axios/axios/pull/11000). For applications running axios >=1.15.1 that cannot immediately upgrade, setting maxRedirects: 0 explicitly on affected HTTP/2 upload calls activates the existing stream byte-counting wrapper and will reject streams that exceed maxBodyLength - note that this disables redirect following for those specific call sites, which is typically acceptable for proxy-to-upstream flows where redirects are not expected but should be verified per application. Applications relying on the default maxBodyLength: -1 or that use string, Buffer, or ArrayBuffer bodies do not require any action. The vendor advisory at https://github.com/axios/axios/security/advisories/GHSA-mwf2-3pr3-8698 should be consulted for authoritative guidance.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-400 – Uncontrolled Resource Consumption
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Linux Enterprise Module for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| openSUSE Leap 16.0 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP5 | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP6 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP3 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today