How severe is CVE-2022-2048?

CVE-2022-2048 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-2048?

CVE-2022-2048 affects the following packages: org.eclipse.jetty.http2:http2-server (Maven), org.eclipse.jetty.http2:http2-server (Maven), org.eclipse.jetty.http2:http2-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-2048?

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.

How do I detect CVE-2022-2048 in my Maven dependencies?

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.

How do I mitigate CVE-2022-2048 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-2048 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-2048 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-2048?

CVE-2022-2048 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-2048?

CVE-2022-2048 is classified as CWE-410 (CWE-410), CWE-664 (CWE-664). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-2048 published, and has it been updated?

CVE-2022-2048 was published on July 7, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-2048 — http2-server

HIGH

CVE-2022-2048 is a high-severity (CVSS 7.5) CWE-410 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

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, 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 CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

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:

Email us at [email protected].

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty.http2:http2-server`	all versions	9.4.47`org.eclipse.jetty.http2:http2-server:9.4.47`
☕Maven	`org.eclipse.jetty.http2:http2-server`	≥ 10.0.0&&< 10.0.10	10.0.10`org.eclipse.jetty.http2:http2-server:10.0.10`
☕Maven	`org.eclipse.jetty.http2:http2-server`	≥ 11.0.0&&< 11.0.10	11.0.10`org.eclipse.jetty.http2:http2-server:11.0.10`

Affected Products

8 products · 12 configurations

debian linuxdebian

2 versions

10.011.0

Application

jettyeclipse

≥ 11.0.0 && < 11.0.9

range

Application

jenkinsjenkins

< 2.361.1

range

Application

element plug-in for vcenter servernetapp

all

Hardware

hci compute nodenetapp

all

Application

management services for element software and netapp hcinetapp

all

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

Product	Fixed in	Advisory
OpenShift Developer Tools and Services for OCP 4.11	`jenkins-0:2.401.1.1686831596-3.el8`	RHSA-2023:3663
Red Hat AMQ Streams 2.3.0	`http2-server`	RHSA-2023:0189
Red Hat Fuse 7.11.1	`http2-server`	RHSA-2022:8652
Red Hat OpenShift Container Platform 4.8	`jenkins-0:2.361.1.1672840472-1.el8`	RHSA-2023:0017
Red Hat OpenShift Container Platform 4.9	`jenkins-0:2.361.1.1675668150-1.el8`	RHSA-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