ubuntu-cve-2026-6790
Vulnerability from osv_ubuntu
Published
2026-07-14 09:16
Modified
2026-07-14 09:16
Summary
Details
In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.
Severity
5.3 (Medium)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.2.14-1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.2.14-1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.2.14-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.2.14-1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.2.14-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.4.15-1~18.04.1ubuntu1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.4.15-1~18.04.1ubuntu1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.4.15-1~18.04.1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.4.15-1~18.04.1ubuntu1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.2.22-2",
"9.2.22-3",
"9.2.23-1",
"9.4.15-1~18.04.1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.4.26-1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.4.26-1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.4.26-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.4.26-1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.4.18-2build2",
"9.4.26-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.4.45-1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.4.45-1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.4.45-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.4.45-1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.4.39-3",
"9.4.44-2",
"9.4.44-3",
"9.4.44-4",
"9.4.45-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.4.53-1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.4.53-1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.4.53-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.4.53-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.4.51-2",
"9.4.53-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty12",
"binary_version": "12.0.32-1"
},
{
"binary_name": "libjetty12-extra-java",
"binary_version": "12.0.32-1"
},
{
"binary_name": "libjetty12-java",
"binary_version": "12.0.32-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "jetty12",
"purl": "pkg:deb/ubuntu/jetty12@12.0.32-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"12.0.17-3.1",
"12.0.32-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "jetty9",
"binary_version": "9.4.58-1"
},
{
"binary_name": "libjetty9-extra-java",
"binary_version": "9.4.58-1"
},
{
"binary_name": "libjetty9-java",
"binary_version": "9.4.58-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "jetty9",
"purl": "pkg:deb/ubuntu/jetty9@9.4.58-1?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"9.4.57-1",
"9.4.57-1.1",
"9.4.58-1"
]
}
],
"aliases": [],
"details": "In Eclipse Jetty, for HTTP/1, HTTP/2 and HTTP/3 requests, there is no strict check that the request authority (host and port) matches what provided in the Host header (if present). This was not enforced in earlier HTTP RFC (for example, in RFC 2616), but it is in the latest RFC (9110 and 9112). This mismatch can cause a number of problems that may be classified as vulnerabilities such as: * URI constructions (for example, for redirects -- this is typical for login pages) * Virtual host selection * Reverse proxying * Misleading logs * Etc. Given that the latest RFCs require that request authority and Host header must match, Jetty should enforce this invariant.",
"id": "UBUNTU-CVE-2026-6790",
"modified": "2026-07-14T09:16:00Z",
"published": "2026-07-14T09:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-6790"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6790"
},
{
"type": "REPORT",
"url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/99"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-6790"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…