A flaw in libsoup’s HTTP header handling allows multiple Host: headers in a request and returns the last occurrence for server-side processing. Common front proxies often honor the first Host: header, so this mismatch can cause vhost confusion where a proxy routes a request to one backend but the backend interprets it as destined for another host. This discrepancy enables request-smuggling style attacks, cache poisoning, or bypassing host-based access controls when an attacker supplies duplicate Host headers.
Metrics
Affected Vendors & Products
References
History
Fri, 12 Dec 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 11 Dec 2025 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 11 Dec 2025 13:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw in libsoup’s HTTP header handling allows multiple Host: headers in a request and returns the last occurrence for server-side processing. Common front proxies often honor the first Host: header, so this mismatch can cause vhost confusion where a proxy routes a request to one backend but the backend interprets it as destined for another host. This discrepancy enables request-smuggling style attacks, cache poisoning, or bypassing host-based access controls when an attacker supplies duplicate Host headers. | |
| Title | Libsoup: libsoup: duplicate host header handling causes host-parsing discrepancy (first- vs last-value wins) | |
| First Time appeared |
Redhat
Redhat enterprise Linux |
|
| Weaknesses | CWE-444 | |
| CPEs | cpe:/o:redhat:enterprise_linux:10 cpe:/o:redhat:enterprise_linux:6 cpe:/o:redhat:enterprise_linux:7 cpe:/o:redhat:enterprise_linux:8 cpe:/o:redhat:enterprise_linux:9 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published: 2025-12-11T12:30:59.266Z
Updated: 2025-12-11T15:05:42.681Z
Reserved: 2025-12-11T07:03:53.445Z
Link: CVE-2025-14523
Updated: 2025-12-11T14:54:32.589Z
Status : Awaiting Analysis
Published: 2025-12-11T13:15:58.983
Modified: 2025-12-12T15:18:13.390
Link: CVE-2025-14523