Client process crash via concurrent session cleanup
Published Apr 8, 2026 · Updated Apr 8, 2026
Improper synchronization in Axios 1.13.0 through 1.13.1 allows remote attackers to crash a Node.js client through HTTP/2 session closures. Http2Sessions.getSession() splices a closed session from its array but continues iterating shifted entries, corrupting cleanup state. Exploitation requires HTTP/2 to be enabled, multiple sessions to an attacker-controlled server, and precisely timed simultaneous closures; impact stays within the client process.
Summary
What happened
Improper synchronization in Axios 1.13.0 through 1.13.1 allows remote attackers to crash a Node.js client through HTTP/2 session closures. Http2Sessions.getSession() splices a closed session from its array but continues iterating shifted entries, corrupting cleanup state. Exploitation requires HTTP/2 to be enabled, multiple sessions to an attacker-controlled server, and precisely timed simultaneous closures; impact stays within the client process.
The record
- CVE
- CVE-2026-39865
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Axios
- Product
- Axios
- Classifications
- CWE-400, CWE-662, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.13.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream concurrent HTTP/2 session-closure procedureproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo