EUVD-2026-25601
GHSA-5c9x-8gcm-mpgx
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
6Blast Radius
ecosystem impact- 273 npm packages depend on axios (189 direct, 84 indirect)
Ecosystem-wide dependent count for version 1.0.0.
DescriptionGitHub Advisory
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, for stream request bodies, maxBodyLength is bypassed when maxRedirects is set to 0 (native http/https transport path). Oversized streamed uploads are sent fully even when the caller sets strict body limits. This vulnerability is fixed in 1.15.1 and 0.31.1.
AnalysisAI
Axios versions prior to 1.15.1 and 0.31.1 allow remote attackers to bypass maxBodyLength restrictions on stream request bodies when maxRedirects is set to 0, enabling denial of service through oversized uploads that consume unbounded server resources. The vulnerability affects the native http/https transport path in Node.js environments and enables attackers to send streamed payloads that exceed configured size limits, potentially exhausting memory or bandwidth on the target application.
Technical ContextAI
Axios is a JavaScript HTTP client library used in Node.js and browser environments to handle HTTP requests. The vulnerability exists in the request body size validation logic, specifically in the native http/https transport handler that processes stream-based request bodies. When maxRedirects is configured to 0 (disabling automatic redirect following), the maxBodyLength validation bypass occurs because the code path for handling stream bodies fails to properly enforce size limits in the direct request scenario. CWE-770 (Allocation of Resources Without Limits or Throttling) describes the root cause: the application fails to enforce configured body size constraints, allowing callers to send arbitrarily large streamed payloads.
RemediationAI
Upgrade Axios to version 1.15.1 or 0.31.1 or later, depending on your major version. For Node.js applications using Axios, apply the patch immediately by running npm update axios or specifying the exact version in package.json and reinstalling. If immediate patching is not feasible, configure maxRedirects to a value greater than 0 (default is 5) to avoid triggering the vulnerable code path, though this does not fully mitigate the risk if stream bodies are still used; alternatively, implement external request body size validation at the application or network layer (e.g., middleware or reverse proxy configuration) to enforce maxBodyLength limits independently of the Axios library. Note that changing maxRedirects has functional implications for redirect handling, so test carefully before deployment. The upstream fix is confirmed in GitHub security advisory GHSA-5c9x-8gcm-mpgx, and patched versions are available from npm.
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 technique Denial Of Service
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today