# io.quarkus:quarkus-resteasy: Memory Leak in Quarkus RESTEasy Classic When Client Requests Timeout Advisory record · `GHSA-4fwr-mh5q-hchh` - **Identifiers:** `GHSA-4fwr-mh5q-hchh` · `CVE-2025-1634` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-401](https://cwe.mitre.org/data/definitions/401.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) - **Published:** 26 Feb 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 26 Feb 2025, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `io.quarkus:quarkus-resteasy` (Maven): affected `>=3.16.0.CR1, <3.19.1 || >=3.9.0.CR1, <3.15.3.1 || <3.8.6.1`; fixed in `3.19.1`, `3.15.3.1`, `3.8.6.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Quarkus RESTEasy Classic (io.quarkus:quarkus-resteasy) versions 3.16.0.CR1 to before 3.19.1, 3.9.0.CR1 to before 3.15.3.1, and before 3.8.6.1 are affected. When client requests time out, a buffer is not released, so memory use grows until the application crashes with an OutOfMemoryError; the source gives few details on what triggers it beyond low client timeouts. Upgrade to 3.19.1, 3.15.3.1, or 3.8.6.1, depending on your release line. No workaround is listed. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (redhat) - **CISA KEV:** Not listed. - **EPSS:** 0.0099, the 63rd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4fwr-mh5q-hchh) ## Sources - [GitHub Advisory Database: GHSA-4fwr-mh5q-hchh](https://github.com/advisories/GHSA-4fwr-mh5q-hchh) - [OSV: GHSA-4fwr-mh5q-hchh](https://osv.dev/vulnerability/GHSA-4fwr-mh5q-hchh) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .