CVE-2026-42039: Axios: unbounded recursion in toFormData causes DoS via deeply nested request data
Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, toFormData recursively walks nested objects with no depth limit, so a deeply nested value passed as request data crashes the Node.js process with a RangeError. This vulnerability is fixed in 1.15.1 and 0.31.1.
Security readout for executives and security teams
Plain-English summary
Axios can be crashed when it processes extremely deeply nested request data in Node.js. The failure is a denial of service: availability is affected, but the sources do not indicate data theft or code execution.
Executive priority
Treat as a high-priority availability risk for Node.js services using axios with user-influenced request data. Prioritize internet-facing or high-traffic services first.
Technical view
Before axios 1.15.1 and 0.31.1, toFormData recursively walks nested objects without a depth limit. Deeply nested request data can trigger a RangeError and crash the Node.js process. CVSS 3.1 is 7.5, with network attack vector and high availability impact.
Likely exposure
Applications are exposed if they use vulnerable axios versions and pass attacker-influenced, deeply nested objects as request data that reaches toFormData. Browser-only or non-attacker-controlled uses may have lower practical exposure.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates unauthenticated network exploitation may be possible where vulnerable data handling is reachable.
Researcher notes
The key condition is reachability of toFormData with deeply nested attacker-controlled data. Sources identify CWE-674 and CWE-770. Evidence does not support claims of confidentiality, integrity impact, RCE, or active exploitation.
Mitigation direction
Upgrade axios to 1.15.1, 0.31.1, or later patched versions.
Check lockfiles and transitive dependencies for vulnerable axios resolutions.
Apply dependency overrides or package manager resolutions where direct upgrades are blocked.
Limit nesting depth for untrusted input before it reaches axios request data.
For Red Hat-packaged software, follow the listed Red Hat advisories.
Validation and detection
Inventory SBOMs, lockfiles, and deployed artifacts for axios versions.
Confirm production resolves axios outside the vulnerable version ranges.
Trace request paths where untrusted data becomes axios request data.
Review error logs for RangeError crashes around request serialization.
Verify scanners map findings to CVE-2026-42039 and the patched versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-674: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-674 · source CWE mapping
Uncontrolled Recursion
Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.