CVE-2026-12611
Reported by eclipse · Published September 8, 2026
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Eclipse Jetty | Eclipse Foundation | 12.1.10, 12.0.37, 11.0.31, 10.0.31, 9.4.63 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Eclipse Foundation | Eclipse Jetty | 12.1.0, 12.0.0, 11.00 |
| Eclipse Foundation | Eclipse Jetty | 12.1.0, 12.0.0, 11.00 |
Timeline
- Sep 8, 2026 Coalition ESS Score
- Sep 8, 2026 CVE Published
- Sep 9, 2026 EPSS Score (23 in total, the first dated here)
- Sep 9, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-12611
vulnetix vdb fixes CVE-2026-12611
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-12611/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart