CVE-2025-1948
published 2025-05-08CVE-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…
PriorityP342high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.63%
46.0th percentile
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.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | jetty12 | < jetty12 12.0.17-1 (forky) | jetty12 12.0.17-1 (forky) |
| debian | jetty9 | < jetty12 12.0.17-1 (forky) | jetty12 12.0.17-1 (forky) |
| eclipse | jetty | >= 12.0.0 < 12.0.17 | 12.0.17 |
| eclipse_foundation | jetty | 12.0.0 – 12.0.16 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv7.5HIGH
vendor_debian7.5HIGH
vendor_oracle7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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
ghsa·2025-05-08
CVE-2025-1948 [HIGH] CWE-400 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
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
### 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
OSV
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
osv·2025-05-08
CVE-2025-1948 [HIGH] 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
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
### 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
OSV
CVE-2025-1948: In Eclipse Jetty versions 12
osv·2025-05-08·CVSS 7.5
CVE-2025-1948 [HIGH] CVE-2025-1948: In Eclipse Jetty versions 12
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.
Oracle
Oracle Oracle Communications Risk Matrix: Security (Eclipse Jetty) — CVE-2025-1948
vendor_oracle·2025-10-15·CVSS 7.5
CVE-2025-1948 [HIGH] Oracle Oracle Communications Risk Matrix: Security (Eclipse Jetty) — CVE-2025-1948
Oracle Oracle Communications Risk Matrix: Security (Eclipse Jetty) vulnerability
CVE: CVE-2025-1948
CVSS: 7.5
Protocol: HTTP
Remote exploit: Yes
Affected versions: Network
Advisory: cpuoct2025 (OCT 2025)
Red Hat
jetty-http2-common: Jetty HTTP/2 Header List Size Vulnerability
vendor_redhat·2025-05-08·CVSS 7.5
CVE-2025-1948 [HIGH] CWE-400 jetty-http2-common: Jetty HTTP/2 Header List Size Vulnerability
jetty-http2-common: Jetty HTTP/2 Header List Size Vulnerability
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.
A flaw was found in Eclipse Jetty. This vulnerability allows denial of service attack via an HTTP/2 client specifying a very large value for the SETTINGS_MAX_HEADER_LIST_SIZE parameter.
Mitigation: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security cr
Debian
CVE-2025-1948: jetty12 - In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can speci...
vendor_debian·2025·CVSS 7.5
CVE-2025-1948 [HIGH] CVE-2025-1948: jetty12 - In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can speci...
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.
Scope: local
forky: resolved (fixed in 12.0.17-1)
sid: resolved (fixed in 12.0.17-1)
trixie: resolved (fixed in 12.0.17-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-05-08
Published