Unauthenticated JVM crash via connection-close race
Published Jul 10, 2025 · Updated Nov 4, 2025
Race condition in Apache Tomcat 8.5.0 through 8.5.100 and 9.0.0.M1 through 9.0.106 allows remote attackers to crash the JVM. AprEndpoint closes an APR socket without consistently holding the socket wrapper lock, allowing a client-initiated HTTP/2 close to race with concurrent native socket operations. APR/native and HTTP/2 must be enabled; successful exploitation interrupts Tomcat service without reported data access or modification.
Summary
What happened
Race condition in Apache Tomcat 8.5.0 through 8.5.100 and 9.0.0.M1 through 9.0.106 allows remote attackers to crash the JVM. AprEndpoint closes an APR socket without consistently holding the socket wrapper lock, allowing a client-initiated HTTP/2 close to race with concurrent native socket operations. APR/native and HTTP/2 must be enabled; successful exploitation interrupts Tomcat service without reported data access or modification.
The record
- CVE
- CVE-2025-52434
- Published
- Jul 10, 2025
- Updated
- Nov 4, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Tomcat
- Classifications
- CWE-362, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=8.5.0 <=8.5.100
- Affected versionversion=9.0.0.M1 <=9.0.106
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
No public exploit references are available in this record.
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