Skip to main content
No exploitation reportedFix available

CVE-2025-1948

No exploitation reported by the sources we read.

  • Published2025-05-08
  • Fixed in12.0.17
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2025-05-0818:15CVE publishedNVD

Versions per branch

NVD · OSV
Eclipse jetty
BranchAffectedFixed in
12.0≥ 12.0.0, < 12.0.1712.0.17

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As eclipse, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Eclipse Foundation Jettyother versions: not affected
    Affected
    • ≥ 12.0.0, ≤ 12.0.16no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-05-08

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-nifiCleanStartall versions · fixed in 2.5.0-r0
  • apache-nifiCleanStartall versions · fixed in 2.5.0-r1
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.3-root.io.3
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.13-root.io.10
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.13-root.io.6
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.13-root.io.7
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.13-root.io.8
  • io.root.org.eclipse.jetty.http2:jetty-http2-commonRoot:Mavenall versions · fixed in 12.0.13-root.io.9

46 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Eclipse jetty to 12.0.17

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2025-05-08
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-400known since 2026-10-23
  • FIRST EPSSEPSS score0.8 %2026-11-06
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2025-05-08

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2025-05-08
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-889j-63jv-qhr8

Frequently asked questions

What is CVE-2025-1948?

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.

Is CVE-2025-1948 actively exploited?

Active exploitation of CVE-2025-1948 has not been confirmed. Its EPSS score was 0.8% on 2026-11-06, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-1948?

CVE-2025-1948 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Jenkins? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record