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.
Security readout for executives and security teams
Plain-English summary
This is a trust-boundary parsing bug in libsoup. If a proxy and backend read duplicate Host headers differently, a request can be routed as one site but processed as another. That can enable cache poisoning or bypass host-based controls. The provided sources do not show active exploitation.
Executive priority
Treat this as a high-priority patching and exposure review item for internet-facing Red Hat workloads. Business urgency is highest where routing, caching, tenant separation, or access control depends on Host headers across proxy and backend layers.
Technical view
libsoup accepts multiple Host headers and uses the last value server-side. Some front proxies commonly use the first value, creating CWE-444 HTTP interpretation inconsistency. Affected Red Hat packages include libsoup, libsoup3, and spice-client-win across listed RHEL 7 ELS, RHEL 8 streams, and RHEL 10/EUS variants.
Likely exposure
Exposure is most likely where affected Red Hat systems run HTTP components using libsoup behind reverse proxies, caches, or host-based access controls. Single-layer deployments without proxy/backend host interpretation differences may have lower practical risk.
Exploitation context
No KEV listing is indicated, and the provided sources do not claim exploitation in the wild. The plausible attack context is remote, unauthenticated traffic reaching a proxied HTTP service where duplicate Host header handling differs between layers.
Researcher notes
The key issue is parser disagreement: first Host value at common front proxies versus last Host value in libsoup server-side processing. Source evidence identifies affected Red Hat packages and advisory references, but does not provide exploit prevalence or detailed fixed-version evidence in this bundle.
Mitigation direction
Review the referenced Red Hat advisories for fixed packages and update affected systems.
Prioritize externally reachable services behind proxies, caches, or virtual-host routing.
Check vendor guidance for non-Red Hat builds or embedded libsoup usage.
Where supported, enforce rejection of malformed requests with duplicate Host headers.
Review host-based access controls that depend on proxy/backend agreement.
Validation and detection
Inventory systems for affected Red Hat products and package names listed in the CVE bundle.
Confirm installed package versions against the relevant Red Hat advisory.
Map services using libsoup that are exposed through reverse proxies or caches.
Review proxy and application logs for malformed Host header rejection or anomalies.
Verify operational controls do not rely solely on backend Host parsing.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-444: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-444 · source CWE mapping
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.