Bug 2576755 (CVE-2026-133200)

Summary: CVE-2026-133200 quarkus-vertx-utils: quarkus-vertx-utils: Denial of Service via worker thread exhaustion on client disconnect
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: ant, aschwart, aszczucz, boliveir, ccranfor, cescoffi, chfoley, cmah, drichtar, ewittman, fmongiar, gsmet, janstey, jmartisk, jnethert, jpechane, jturenov, kaycoth, manderse, mposolda, nipatil, olubyans, ozzy, pantinor, pjindal, rguimara, rkubis, rmartinc, sbiarozk, sdawley, ssilvert, sthorger, swoodman, tmielke, varjain, vmuzikar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in quarkus-vertx-utils. When a client disconnects while receiving a streaming response, the server fails to detect the closed connection and continues processing the data indefinitely. An unauthenticated remote attacker can exploit this issue by repeatedly initiating streaming requests and disconnecting, exhausting worker threads and resulting in a Denial of Service (DoS).
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-19 15:02:30 UTC
A flaw was found in quarkus-vertx-utils. When a Quarkus REST endpoint returns a blocking streaming body (InputStream, StreamingOutput) and the client disconnects, VertxOutputStream does not detect the closed connection unless the Vert.x write queue is full. After a disconnect, Vert.x discards writes without filling the queue, so the worker thread keeps reading from the source and writing into the closed response indefinitely. An unauthenticated remote client can open such a response, disconnect, and repeat until every worker thread is stuck, causing a denial of service. Stuck threads are not released until the application restarts.