CVE-2025-66560: Quarkus REST has potential worker thread starvation when HTTP connection is closed while waiting to write
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. ## Workarounds For versions without the fix applied, it is recommended to implement a health check that monitors the status and saturation of the worker thread pool. This helps detect abnormal thread retention early and allows operators to take corrective action before the application’s responsiveness is impacted. ## Credits CVE reported by Shaswata Jash, Nokia
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-66560?
The severity of CVE-2025-66560 is considered to be significant due to its impact on the HTTP response handling in Quarkus REST.
How do I fix CVE-2025-66560?
To fix CVE-2025-66560, upgrade to Quarkus versions 3.31.0, 3.27.2, or 3.20.5 or later.
What versions of Quarkus are affected by CVE-2025-66560?
CVE-2025-66560 affects Quarkus versions prior to 3.31.0, 3.27.2, and 3.20.5.
What kind of functionality is impacted by CVE-2025-66560?
CVE-2025-66560 impacts the HTTP layer of Quarkus REST, specifically related to how responses are handled.
Is CVE-2025-66560 a remote code execution vulnerability?
CVE-2025-66560 is not a remote code execution vulnerability, but it poses risks associated with improper response handling.