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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-1948
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 11:24 UTC · Revision 1
Source evidence
Eclipse Jetty HTTP clients can increase memory allocation
core-osv · Original sourcePublished 8 May 2025, 17:48 UTC
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.
osv:CVE-2025-1948
Complete source record
{
"id": "fe65ef1f62d700d797026e282604afbcdbb17175836b34d6a4f3301c9272b8db",
"url": "https://osv.dev/vulnerability/CVE-2025-1948",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Eclipse Jetty HTTP clients can increase memory allocation",
"summary": "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.",
"evidence": "osv:CVE-2025-1948",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2025-1948",
"aliases": [
"CVE-2025-1948",
"GHSA-889j-63jv-qhr8"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/jetty/jetty.project",
"type": "GIT",
"events": [
{
"introduced": "28100e8da711e44c0722ed10bd413ae862497539"
},
{
"fixed": "14d19c268e4cb09afc312b5255a4cbb7a95c5cb6"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "12.0.0"
},
{
"last_affected": "12.0.16"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"cpe": "cpe:2.3:a:eclipse:jetty:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "12.0.0"
},
{
"fixed": "12.0.17"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"jetty-12.0.15",
"jetty-12.0.14",
"jetty-12.0.6",
"jetty-12.0.5",
"jetty-12.0.0x"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-1948.json"
}
}
],
"modified": "2026-10-28T02:30:28.167724541Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1948.json",
"https://github.com/jetty/jetty.project/security/advisories/GHSA-889j-63jv-qhr8",
"https://nvd.nist.gov/vuln/detail/CVE-2025-1948",
"https://gitlab.eclipse.org/security/cve-assignement/-/issues/56"
],
"provider_metadata": {
"cwe_ids": [
"CWE-400"
],
"cna_assigner": "eclipse",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/1xxx/CVE-2025-1948.json"
}
},
"related_cves": [
{
"value": "CVE-2025-1948",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 494936,
"published_at": "2025-05-08T17:48:40.831+00:00"
}