Skip to content
fr Sign in
8.7 High

CVE-2026-12611 A client may issue HTTP/2 requests to a Jetty server that result in blocking writes that are never unblocked, eventually…

Description

A client may issue HTTP/2 requests to a Jetty server that result in blocking writes that are never unblocked, eventually causing all threads to be blocked and the whole server to become unresponsive. This is caused by a race condition in the server when handling RST_STREAM frames and GOAWAY frames sent by the client. The race condition "resets" the HTTP2Flusher.terminated, previously set to a non-null value, to the null value, allowing entries to be enqueued in the flusher that however will never be processed. These unprocessed entries are the ones that would unblock the write-blocked threads.

Affected products and versions

Product Affected versions Fixed in
Eclipse Jetty 12.1 12.1.0 → 12.1.10 No fix stated
Eclipse Jetty 12.0 12.0.0 → 12.0.37 No fix stated
Eclipse Jetty 11.00 11.00 → 11.0.31 No fix stated
Eclipse Jetty 10.0 10.0.0 → 10.0.31 No fix stated
Eclipse Jetty 9.4 9.4.36 → 9.4.63 No fix stated

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Eclipse Jetty

The 16 CVEs of Eclipse Jetty →
CVE-2026-18661 In Eclipse Jetty, across various versions of `jetty-annotations`, and `jetty-eeN-annotations`, the Jakarta Spec… 8.8 High CVE-2026-77711 When Jetty's `HttpClient` make a request to a server through a forward proxy, the server may reply with a 407 (Proxy… 8.2 High CVE-2026-76184 In Eclipse Jetty, HttpClient may receive a redirect of the form: ``` /secure/../evil ``` If an attacker is able to… 8.2 High CVE-2026-76182 In Eclipse Jetty, `TryPathsHandler` and `TryFilesFilter` can be configured to forward requests to template URIs such… 6.9 Medium
Track this CVE