Advisory record · GHSA-4fwr-mh5q-hchh

io.quarkus:quarkus-resteasy: Memory Leak in Quarkus RESTEasy Classic When Client Requests Timeout

CVSS 7.5 HighEPSS 0.0099 · 63rd percentile

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.

PackageEcosystemAffectedFixed in
io.quarkus:quarkus-resteasyMaven>=3.16.0.CR1, <3.19.1 || >=3.9.0.CR1, <3.15.3.1 || <3.8.6.13.19.1, 3.15.3.1, 3.8.6.1
Identifiers
GHSA-4fwr-mh5q-hchh · CVE-2025-1634
Weakness (CWE)
CWE-401
Published
26 Feb 2025
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 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

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

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.