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

CVE-2022-2048 — http2-server

HIGH

CVE-2022-2048 is a high-severity (CVSS 7.5) vulnerability in org.eclipse.jetty.http2:http2-server. A fix is available for org.eclipse.jetty.http2:http2-server — see the affected versions and patch details below.

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

Also known asBIT-jenkins-2022-2048GHSA-wgmr-mf83-7x4j
Published
Jul 7, 2022
Updated
Sep 6, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% 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

CVE-2022-2048 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 378,567 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

3 pkgs affected
☕org.eclipse.jetty.http2:http2-server☕org.eclipse.jetty.http2:http2-server☕org.eclipse.jetty.http2:http2-server

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

Description

Invalid HTTP/2 requests (for example, invalid URIs) are incorrectly handled by writing a blocking error response directly from the selector thread. If the client manages to exhaust the HTTP/2 flow control window, or TCP congest the connection, the selector thread will be blocked trying to write the error response. If this is repeated for all the selector threads, the server becomes unresponsive, causing the denial of service.

Impact

A malicious client may render the server unresponsive.

Patches

The fix is available in Jetty versions 9.4.47. 10.0.10, 11.0.10.

Workarounds

No workaround available within Jetty itself. One possible workaround is to filter the requests before sending them to Jetty (for example in a proxy)

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.jetty.http2:http2-serverall versions9.4.47org.eclipse.jetty.http2:http2-server:9.4.47
☕Mavenorg.eclipse.jetty.http2:http2-server≥ 10.0.0&&< 10.0.1010.0.10org.eclipse.jetty.http2:http2-server:10.0.10
☕Mavenorg.eclipse.jetty.http2:http2-server≥ 11.0.0&&< 11.0.1011.0.10org.eclipse.jetty.http2:http2-server:11.0.10

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-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.eclipse.jetty.http2:http2-server to 9.4.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2048 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 CVE-2022-2048 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-2048. 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
ProductFixed inAdvisory
OpenShift Developer Tools and Services for OCP 4.11jenkins-0:2.401.1.1686831596-3.el8RHSA-2023:3663
Red Hat AMQ Streams 2.3.0http2-serverRHSA-2023:0189
Red Hat Fuse 7.11.1http2-serverRHSA-2022:8652
Red Hat OpenShift Container Platform 4.8jenkins-0:2.361.1.1672840472-1.el8RHSA-2023:0017
Red Hat OpenShift Container Platform 4.9jenkins-0:2.361.1.1675668150-1.el8RHSA-2023:0777

Frequently Asked Questions

### Description Invalid HTTP/2 requests (for example, invalid URIs) are incorrectly handled by writing a blocking error response directly from the selector thread. If the client manages to exhaust the HTTP/2 flow control window, or TCP congest the connection, the selector thread will be blocked trying to write the error response. If this is repeated for all the selector threads, the server becomes unresponsive, causing the denial of service. ### Impact A malicious client may render the server unresponsive. ### Patches The fix is available in Jetty versions 9.4.47. 10.0.10, 11.0.10. ### Work
O3 Security · Impact-Aware SCA

Is CVE-2022-2048 in your dependencies?

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

Scan my dependencies How O3 SCA works
CVE-2022-2048: http2-server DoS (High 7.5) | O3 Security