Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-66560
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 11:26 UTC · Revision 1
Source evidence
Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write
core-osv · Original sourcePublished 7 Jan 2026, 17:33 UTC
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.
osv:CVE-2025-66560
Complete source record
{
"id": "e94d015c3e1d541e733a5208c576b0eb8e03b45d48dfdabe9f5dc5eecaafb3a3",
"url": "https://osv.dev/vulnerability/CVE-2025-66560",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write",
"summary": "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.",
"evidence": "osv:CVE-2025-66560",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2025-66560",
"aliases": [
"CVE-2025-66560",
"GHSA-5rfx-cp42-p624"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/quarkusio/quarkus",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "59263d5c0609fcf5831a0335ae651d7cf4ef1a78"
},
{
"introduced": "15d328f8fabbae10e97c9ce38f30e4d8a1f104fc"
},
{
"fixed": "f1f20c8061bd076ae8fec685eb488453ab6ad491"
},
{
"introduced": "2201e3ff9218a6d0602eb91b1fd39f711f04f3ef"
},
{
"fixed": "d4a4f24c9953fe59a42673ea36c57cfdad5a9371"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:quarkus:quarkus:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "3.20.5"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:quarkus:quarkus:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.21.0"
},
{
"fixed": "3.27.2"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:quarkus:quarkus:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.30.0"
},
{
"fixed": "3.31.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-66560.json"
}
}
],
"modified": "2026-10-28T02:30:43.991348025Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/66xxx/CVE-2025-66560.json",
"https://github.com/quarkusio/quarkus/security/advisories/GHSA-5rfx-cp42-p624",
"https://nvd.nist.gov/vuln/detail/CVE-2025-66560"
],
"provider_metadata": {
"cwe_ids": [
"CWE-770"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/66xxx/CVE-2025-66560.json"
}
},
"related_cves": [
{
"value": "CVE-2025-66560",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 511727,
"published_at": "2026-01-07T17:33:22.083+00:00"
}