Advisory record · GHSA-5rfx-cp42-p624

Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write

CVSS 5.9 MediumEPSS 0.0038 · 32nd percentile

Published by the GitHub Advisory Database at 7 Jan 2026, 18:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.quarkus:quarkus-restMaven<3.20.5 || >=3.21.0, <3.27.2 || >=3.30.0, <3.31.03.20.5, 3.27.2, 3.31.0
Identifiers
GHSA-5rfx-cp42-p624 · CVE-2025-66560
Weakness (CWE)
CWE-770
Published
7 Jan 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Quarkus REST (io.quarkus:quarkus-rest, Maven) versions before 3.20.5, from 3.21.0 before 3.27.2, and from 3.30.0 before 3.31.0 are affected. When a client drops its connection while a response is being written, a worker thread can remain permanently blocked, and repeated occurrences can exhaust the worker thread pool and make the application slow or unavailable. Upgrade to 3.20.5, 3.27.2, or 3.31.0, depending on your release line. The source suggests monitoring worker thread pool saturation as an interim measure.

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
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0038, the 32nd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 7 Jan 2026, 15:15 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:18 UTC First seen by agentprime
  3. 31 Oct 2026, 14:18 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.