CVE-2025-66560

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

HIGH
7.5
CVSS Score
Published: January 7, 2026 at 05:33 PM UTC
Updated: October 7, 2026 at 09:10 AM UTC
2 products affected across 2 vendorsQuarkusQuarkus

Using quarkus by quarkusio?

Get instant alerts when new vulnerabilities affect quarkus - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

Quarkus is a Cloud Native, (Linux) Container First framework for writing Java applications. Prior to versions 3.31.0, 3.27.2, and 3.20.5, a vulnerability exists in the HTTP layer of Quarkus REST related to response handling. When a response is being written, the framework waits for previously written response chunks to be fully transmitted before proceeding. If the client connection is dropped during this waiting period, the associated worker thread is never released and becomes permanently blocked. Under sustained or repeated occurrences, this can exhaust the available worker threads, leading to degraded performance, or complete unavailability of the application. This issue has been patched in versions 3.31.0, 3.27.2, and 3.20.5. A workaround involves implementing a health check that monitors the status and saturation of the worker thread pool to detect abnormal thread retention early.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.20.53.21.0 ≤ v < 3.27.23.30.0 ≤ v < 3.31.0
Affected range stops below 3.20.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.27.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.31.0, so it looks safe — our inference, not a vendor statement
v < 3.20.5v < 3.27.2v < 3.31.0
Affected range stops below 3.20.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.27.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.31.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/quarkusio/quarkus/security/advisories/GHSA-5rfx-cp42-p624

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card