CVE-2026-67318 axios CVE debrief

Who should care

Teams using axios (>=1.13.0) with Node.js HTTP adapter and HTTP/2 should review and adjust maxBodyLength configurations to prevent potential resource consumption and policy bypass. Affected operators should verify axios version and HTTP/2 usage. Security teams should monitor for suspicious egress and quota consumption.

Technical summary

axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce maxBodyLength limit on streamed request bodies when using httpVersion: 2. This allows an attacker to cause excessive outbound data transmission, leading to resource consumption and potential policy bypass. The vulnerability impacts resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control.

Defensive priority

Medium-priority defensive actions are recommended due to potential resource consumption and policy bypass impacts.

Recommended defensive actions

• Verify axios version is within affected range (>=1.13.0) and HTTP/2 is in use.
• Review and adjust maxBodyLength configuration.
• Monitor for suspicious outbound data transmission and resource consumption.
• Implement compensating controls to limit egress and quota consumption.
• Review relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce maxBodyLength limit on streamed request bodies when using httpVersion: 2. This allows an attacker to cause excessive outbound data transmission, leading to resource consumption and potential policy bypass. Evidence is limited; verify axios version and HTTP/2 usage. Monitor for suspicious egress and quota consumption. The CVE record was published on 2026-08-01T13:17:01.947Z and has not been modified since then. No additional information is available.

Sources and references

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.