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

高 7.5CVE-2025-66560 · GHSA-5rfx-cp42-p624 · 07/01/2026 公開 · 07/10/2026 更新

要点

CVE-2025-66560 は io.quarkus:quarkus-rest, quarkus (quarkus) に影響する深刻度「高」 (CVSS 7.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.38%（全脆弱性の 32.3% より高い）。
対処：3.27.2, 3.31.0, 3.20.5 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
io.quarkus:quarkus-rest Maven	`≥ 3.21.0, < 3.27.2≥ 3.30.0, < 3.31.0< 3.20.5`	`3.27.23.31.03.20.5`
quarkus quarkus	`≥ 3.21.0, < 3.27.2≥ 3.30.0, < 3.31.0< 3.20.5`	`3.27.23.31.03.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.

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

NVD の説明

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.