PatchSiren cyber security CVE debrief
CVE-2026-67321 axios CVE debrief
Axios before 0.33.0 contains an incomplete depth-limit bypass in toFormData.js when serializing objects with top-level keys ending in '{}'. This vulnerability can cause a RangeError from JSON.stringify, potentially leading to denial of service in the affected request path due to excessive recursion. Developers and security teams should assess exposure and prioritize remediation based on operational impact and asset criticality. The CVE record was published on 2026-08-01T13:17:02.360Z and has not been modified since then. Further review is needed to assess affected scope, impact, and verify with source details.
- Vendor
- axios
- Product
- Unknown
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-01
- Original CVE updated
- 2026-09-01
- Advisory published
- 2026-08-01
- Advisory updated
- 2026-09-01
Who should care
Developers and administrators using axios versions before 0.33.0 should review and potentially update to mitigate potential denial of service via incomplete depth-limit bypass. Security teams and vulnerability management teams should assess exposure and prioritize remediation based on operational impact and asset criticality.
Technical summary
Axios before 0.33.0 contains an incomplete depth-limit bypass in toFormData.js when serializing objects with top-level keys ending in '{}'. This can cause a RangeError from JSON.stringify, potentially leading to denial of service in the affected request path due to excessive recursion. The vulnerability affects request paths using axios form or parameter serialization. Security teams and vulnerability management teams should assess exposure and prioritize remediation based on operational impact and asset criticality. Review axios versions before 0.33.0 for potential vulnerability and consider upgrading axios to version 0.33.0 or later.
Defensive priority
Medium-priority defensive review recommended due to potential denial of service via incomplete depth-limit bypass.
Recommended defensive actions
- Review axios versions before 0.33.0 for potential vulnerability
- Assess if applications using axios are exposed to denial of service via incomplete depth-limit bypass
- Consider upgrading axios to version 0.33.0 or later
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
Evidence from official CVE and NVD sources indicates an incomplete depth-limit bypass in axios toFormData.js, potentially affecting request paths. Further review needed to assess affected scope, impact, and verify with source details.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-67321 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-67321
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-67321 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-67321
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/axios/axios/security/advisories/GHSA-hcpx-6fm6-wx23
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/axios-before-denial-of-service-via-maxdepth-bypass
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.