CVE-2025-1948 | Eclipse Jetty HTTP clients can increase memory allocation

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.

Published: 2025-05-08 Last update: 2025-07-31 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-1948 is rated Moderate Risk (54.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.58%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-1948

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 0.47% 0.58% +0.11%
2 2026-04-21 0.58% 0.47% -0.11%
3 2026-03-04 — 0.58% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-1948

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-1948

GitHub Security Advisory for CVE-2025-1948

GHSA-889j-63jv-qhr8 · Severity: high · Ecosystem: maven — Eclipse Jetty HTTP/2 client can force the server to allocate a humongous byte buffer that may lead to OoM and subsequently the JVM to exit

OS Trackers for CVE-2025-1948

vendor priority summary link
debian unimportant CVE-2025-1948 unimportant priority: Debian including 2 source packages (jetty12, jetty9), 8 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 8. https://security-tracker.debian.org/tracker/CVE-2025-1948
redhat high — https://access.redhat.com/security/cve/CVE-2025-1948
ubuntu medium CVE-2025-1948 medium priority: Ubuntu including 3 source packages (jetty, jetty12, jetty9), 20 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 8, needs-triage 8, not-affected 2, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-1948

Affected software / configurations for CVE-2025-1948

Vendor Product Version Raw CPE
eclipse jetty >= 12.0.0, < 12.0.17 cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*

References for CVE-2025-1948

cvelogic Threat Intelligence