Advisory record · GHSA-wgmr-mf83-7x4j

Jetty vulnerable to Invalid HTTP/2 requests that can lead to denial of service

CVSS 7.5 HighEPSS 0.026 · 85th percentile

Published by the GitHub Advisory Database at 7 Jul 2022, 20:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.eclipse.jetty.http2:http2-serverMaven<9.4.47 || >=10.0.0, <10.0.10 || >=11.0.0, <11.0.109.4.47, 10.0.10, 11.0.10
Identifiers
GHSA-wgmr-mf83-7x4j · BIT-jenkins-2022-2048 · CVE-2022-2048
Weakness (CWE)
CWE-400 · CWE-410 · CWE-664
Published
7 Jul 2022
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jetty's http2-server package (Maven org.eclipse.jetty.http2:http2-server) versions before 9.4.47, from 10.0.0 before 10.0.10, and from 11.0.0 before 11.0.10 are affected. A remote client can send invalid HTTP/2 requests, such as ones with invalid URIs, and exhaust the flow control window or congest the TCP connection so that the selector threads block while writing error responses, making the server unresponsive. Upgrade to 9.4.47, 10.0.10, or 11.0.10. The source lists no workaround within Jetty; it suggests filtering such requests before they reach Jetty, for example in a proxy.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (eclipse)
  • CISA KEV Not listed.
  • EPSS 0.026, the 85th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.