Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-rggv-cv7r-mw98 http2-common

HIGHFix: jetty/jetty.project@0839a20

GHSA-rggv-cv7r-mw98 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.eclipse.jetty.http2:http2-common. A fix is available for org.eclipse.jetty.http2:http2-common — see the affected versions and patch details below.

Connection leaking on idle timeout when TCP congested

Also known asCVE-2024-22201
Published
Feb 26, 2024
Updated
Sep 10, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rggv-cv7r-mw98.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-rggv-cv7r-mw98 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

7 pkgs affected
org.eclipse.jetty.http2:http2-commonorg.eclipse.jetty.http2:http2-commonorg.eclipse.jetty.http3:http3-commonorg.eclipse.jetty.http2:http2-commonorg.eclipse.jetty.http3:http3-commonorg.eclipse.jetty.http2:jetty-http2-commonorg.eclipse.jetty.http3:jetty-http3-common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

If an HTTP/2 connection gets TCP congested, when an idle timeout occurs the HTTP/2 session is marked as closed, and then a GOAWAY frame is queued to be written. However it is not written because the connection is TCP congested. When another idle timeout period elapses, it is then supposed to hard close the connection, but it delegates to the HTTP/2 session which reports that it has already been closed so it does not attempt to hard close the connection.

This leaves the connection in ESTABLISHED state (i.e. not closed), TCP congested, and idle.

An attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients.

The client may also be impacted (if the server does not read causing a TCP congestion), but the issue is more severe for servers.

Patches

Patched versions:

  • 9.4.54
  • 10.0.20
  • 11.0.20
  • 12.0.6

Workarounds

Disable HTTP/2 and HTTP/3 support until you can upgrade to a patched version of Jetty. HTTP/1.x is not affected.

References

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.eclipse.jetty.http2:http2-common9.3.0&&< 9.4.549.4.54org.eclipse.jetty.http2:http2-common:9.4.54
Mavenorg.eclipse.jetty.http2:http2-common10.0.0&&< 10.0.2010.0.20org.eclipse.jetty.http2:http2-common:10.0.20
Mavenorg.eclipse.jetty.http3:http3-common10.0.8&&< 10.0.2010.0.20org.eclipse.jetty.http3:http3-common:10.0.20
Mavenorg.eclipse.jetty.http2:http2-common11.0.0&&< 11.0.2011.0.20org.eclipse.jetty.http2:http2-common:11.0.20
Mavenorg.eclipse.jetty.http3:http3-common11.0.8&&< 11.0.2011.0.20org.eclipse.jetty.http3:http3-common:11.0.20
Mavenorg.eclipse.jetty.http2:jetty-http2-common12.0.0&&< 12.0.612.0.6org.eclipse.jetty.http2:jetty-http2-common:12.0.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.jetty.http2:http2-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.eclipse.jetty.http2:http2-common to 9.4.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rggv-cv7r-mw98 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rggv-cv7r-mw98 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rggv-cv7r-mw98. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The issue in Jetty where HTTP/2 connections can enter a congested, idle state and potentially exhaust server file descriptors represents a moderate severity due to its impact on system resources and service availability. While the vulnerability requires the deliberate creation of numerous congested connections by an…

ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-0:2.440.3.1716445200-3.el8RHSA-2024:3635
OCP-Tools-4.13-RHEL-8jenkins-0:2.440.3.1716445150-3.el8RHSA-2024:3636
OCP-Tools-4.14-RHEL-8jenkins-0:2.440.3.1716387933-3.el8RHSA-2024:3634
OCP-Tools-4.15-RHEL-8jenkins-0:2.440.3.1718879390-3.el8RHSA-2024:4597
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2jettyRHSA-2024:4884
Red Hat build of Apicurio Registry 2.6.1 GAjettyRHSA-2024:4873

Frequently Asked Questions

### Impact If an HTTP/2 connection gets TCP congested, when an idle timeout occurs the HTTP/2 session is marked as closed, and then a GOAWAY frame is queued to be written. However it is not written because the connection is TCP congested. When another idle timeout period elapses, it is then supposed to hard close the connection, but it delegates to the HTTP/2 session which reports that it has already been closed so it does not attempt to hard close the connection. This leaves the connection in ESTABLISHED state (i.e. not closed), TCP congested, and idle. An attacker can cause many connection
O3 Security · Impact-Aware SCA

Is GHSA-rggv-cv7r-mw98 in your dependencies?

O3 Security finds GHSA-rggv-cv7r-mw98 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rggv-cv7r-mw98: http2-common | O3 Security