Application crash via unreleased response output stream
Published Feb 26, 2025 · Updated May 6, 2026
Memory leak in Quarkus RESTEasy Classic allows remote attackers to crash affected applications through aborted HTTP requests. VertxHttpResponse.finish returns after a response closes without closing its output stream, leaving pooled buffers retained after each aborted request. Repeated low-timeout requests require no authentication and progressively exhaust heap memory until an OutOfMemoryError crashes the application.
Summary
What happened
Memory leak in Quarkus RESTEasy Classic allows remote attackers to crash affected applications through aborted HTTP requests. VertxHttpResponse.finish returns after a response closes without closing its output stream, leaving pooled buffers retained after each aborted request. Repeated low-timeout requests require no authentication and progressively exhaust heap memory until an OutOfMemoryError crashes the application.
The record
- CVE
- CVE-2025-1634
- Published
- Feb 26, 2025
- Updated
- May 6, 2026
- Vendor
- Quarkus
- Product
- Quarkus
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 6, 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=0 <3.15.3
- Affected versionversion=0 <3.8.6
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
- Quarkus issue 46412 reproducerproof of concept · demonstrated
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