CVE-2025-1634: Io.quarkus:quarkus-resteasy: memory leak in quarkus resteasy classic when client requests timeout
A flaw was found in the quarkus-resteasy extension, which causes memory leaks when client requests with low timeouts are made. If a client request times out, a buffer is not released correctly, leading to increased memory usage and eventual application crash due to OutOfMemoryError.
Security readout for executives and security teams
Plain-English summary
CVE-2025-1634 is a high-severity availability flaw in quarkus-resteasy. Timed-out client requests can leave buffers unreleased, causing memory growth and eventual OutOfMemoryError crashes. The provided evidence indicates service disruption risk, not data theft or unauthorized modification.
Executive priority
Treat this as a high-priority availability risk for Quarkus API services. It can crash affected applications without authentication, so production internet-facing services should be assessed and patched promptly through vendor-supported updates.
Technical view
The flaw is a CWE-401 memory leak in the Quarkus RESTEasy extension. CVSS is 7.5: network reachable, low complexity, no privileges, no user interaction, with high availability impact only. The bundle lists Red Hat build of Quarkus 3 as affected.
Likely exposure
Exposure is most likely in services running Red Hat build of Quarkus 3 with quarkus-resteasy, especially externally reachable APIs. Several named Red Hat product versions are marked unaffected in the bundle, so teams should verify exact product, dependency, and vendor status.
Exploitation context
The bundle does not support active exploitation; KEV is false. The described abuse path is availability-focused: repeated requests that timeout can cause unreleased memory and eventual application crash. No source indicates confidentiality or integrity impact.
Researcher notes
Evidence points to a timeout-triggered buffer release failure in quarkus-resteasy. The affected matrix is narrow in the supplied bundle: Red Hat build of Quarkus 3 is affected, while several specific Red Hat products are listed unaffected. Do not assume broader product impact without vendor confirmation.
Mitigation direction
Apply the relevant Red Hat advisory updates where they apply.
Check Red Hat CVE guidance for exact fixed package versions.
Inventory Quarkus services using quarkus-resteasy or RESTEasy Classic.
Prioritize externally reachable services and high-availability workloads.
Monitor memory growth and OutOfMemoryError events until patched.
Validation and detection
Confirm whether applications use Red Hat build of Quarkus 3.
Check dependency trees for quarkus-resteasy presence.
Compare installed packages against Red Hat advisory applicability.
Review service logs for request timeouts followed by memory growth.
Verify patched deployments no longer show sustained leak behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.