Quick answers
- Is CVE-2026-42034 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42034 being exploited in the wild.
- How severe is CVE-2026-42034?
- Medium severity, with a CVSS score of 5.3, published 24 April 2026.
- Which products and versions are affected?
- axios (npm) SEMVER:introduced=1.0.0,fixed=1.15.1.
- Is there a fix for CVE-2026-42034?
- Yes. axios (npm): upgrade to 1.15.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42034 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-42034?
- Check whether you run Axios or axios (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- axios (npm): upgrade to 1.15.1 or later
npm install axios@1.15.1
Technical details
This vulnerability is a resource exhaustion weakness (CWE-770) where Axios fails to enforce the maxBodyLength limit on streamed request bodies when maxRedirects is configured to 0. The root cause lies in lib/adapters/http.js: the maxBodyLength check (lines 556-564) only applies to buffered/non-stream data; when maxRedirects === 0, the native http/https transport is selected (lines 681-682); and the stream is piped directly to the socket without Axios-level byte counting (lines 925-945), bypassing the intended limit enforcement. An attacker can send a 2 MiB stream with maxBodyLength: 1024 and maxRedirects: 0, and it will be transmitted in full despite the configured limit. The vulnerability affects all versions up to and including Axios 1.15.0 and 0.31.0, with patches available in 1.15.1 and 0.31.1. No authentication or user interaction is required; the attack is network-accessible and occurs through a direct API call with specific parameters.
Affected products
- axios axios < 0.31.1 and 1.0.0 to <= 1.15.0
Identifiers
- CVE-2026-42034
- GHSA-5c9x-8gcm-mpgx
Timeline
- 2026-04-24: disclosed
- 2026-05-05: patched: Patches released in versions 1.15.1 and 0.31.1