How severe is CVE-2025-1948?

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

Which packages are affected by CVE-2025-1948?

CVE-2025-1948 affects the following packages: org.eclipse.jetty.http2:jetty-http2-common (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-1948?

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

How do I detect CVE-2025-1948 in my Maven dependencies?

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

How do I mitigate CVE-2025-1948 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-2025-1948 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-1948 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-2025-1948?

CVE-2025-1948 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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-2025-1948?

CVE-2025-1948 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-1948 published, and has it been updated?

CVE-2025-1948 was published on May 8, 2025 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-2025-1948 — jetty-http2-common

HIGHFix: jetty/jetty.project@c8c2515

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

Eclipse Jetty HTTP clients can increase memory allocation

Also known asGHSA-889j-63jv-qhr8

Published

May 8, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-1948.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs57th percentile — riskier than 57% 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

1 pkg affected

☕org.eclipse.jetty.http2:jetty-http2-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

Original Report

In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can specify a very large value for the HTTP/2 settings parameter SETTINGS_MAX_HEADER_LIST_SIZE. The Jetty HTTP/2 server does not perform validation on this setting, and tries to allocate a ByteBuffer of the specified capacity to encode HTTP responses, likely resulting in OutOfMemoryError being thrown, or even the JVM process exiting.

Impact

Remote peers can cause the JVM to crash or continuously report OOM.

Patches

12.0.17

Workarounds

No workarounds.

References

https://github.com/jetty/jetty.project/issues/12690

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.jetty.http2:jetty-http2-common`	≥ 12.0.0&&< 12.0.17	12.0.17`org.eclipse.jetty.http2:jetty-http2-common:12.0.17`

Affected Products

1 product · 1 configurations

Application

jettyeclipse

≥ 12.0.0 && < 12.0.17

range

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:jetty-http2-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.jetty.http2:jetty-http2-common to 12.0.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-1948 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 HatImportant

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-1948 (CC BY 4.0)

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.504.2.1750932984-3.el8`	RHSA-2025:10118
OCP-Tools-4.13-RHEL-8	`jenkins-0:2.504.2.1750916374-3.el8`	RHSA-2025:10119
OCP-Tools-4.14-RHEL-8	`jenkins-0:2.504.2.1750903189-3.el8`	RHSA-2025:10120
OCP-Tools-4.15-RHEL-8	`jenkins-0:2.504.2.1750856366-3.el8`	RHSA-2025:10104
OCP-Tools-4.16-RHEL-9	`jenkins-0:2.504.2.1750857144-3.el9`	RHSA-2025:10098
OCP-Tools-4.17-RHEL-9	`jenkins-0:2.504.2.1750851690-3.el9`	RHSA-2025:10097
OCP-Tools-4.18-RHEL-9	`jenkins-0:2.504.2.1750846524-3.el9`	RHSA-2025:10092
Red Hat AMQ Broker 7.13.1	`jetty-http2-common`	RHSA-2025:13274

Frequently Asked Questions

### Original Report In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can specify a very large value for the HTTP/2 settings parameter SETTINGS_MAX_HEADER_LIST_SIZE. The Jetty HTTP/2 server does not perform validation on this setting, and tries to allocate a ByteBuffer of the specified capacity to encode HTTP responses, likely resulting in OutOfMemoryError being thrown, or even the JVM process exiting. ### Impact Remote peers can cause the JVM to crash or continuously report OOM. ### Patches 12.0.17 ### Workarounds No workarounds. ### References https://github.com/jet