CVE-2026-5119: Libsoup: libsoup: information disclosure via cleartext transmission of cookies during https tunnel establishment
A flaw was found in libsoup. When establishing HTTPS tunnels through a configured HTTP proxy, sensitive session cookies are transmitted in cleartext within the initial HTTP CONNECT request. A network-positioned attacker or a malicious HTTP proxy can intercept these cookies, leading to potential session hijacking or user impersonation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-5119 can expose session cookies when a libsoup-based application connects to HTTPS through an HTTP proxy. The cookies may be sent in cleartext during tunnel setup, letting a malicious proxy or network-positioned attacker steal sessions. The issue is medium severity but important where proxying and authenticated applications overlap.
Executive priority
Treat this as targeted remediation, not an emergency. Patch affected proxy-using RHEL systems promptly, especially where session cookies protect business applications or privileged workflows.
Technical view
libsoup and libsoup3 may include sensitive cookies in the initial HTTP CONNECT request used to establish an HTTPS tunnel through a configured HTTP proxy. Because CONNECT setup is cleartext to the proxy, cookies can be disclosed before TLS protects the target connection. Red Hat lists affected RHEL streams and package builds for libsoup/libsoup3.
Likely exposure
Exposure is most likely on affected Red Hat Enterprise Linux systems running applications that use libsoup or libsoup3, authenticate with cookies, and route HTTPS traffic through configured HTTP proxies.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. Practical abuse requires a malicious proxy or suitable network position and a victim workflow that sends relevant cookies through libsoup during HTTPS tunnel establishment.
Researcher notes
Key validation is whether cookies are attached to CONNECT requests in affected builds and whether an HTTP proxy can observe them. The source bundle supports disclosure and potential hijacking impact, but not active exploitation or broad product claims beyond listed Red Hat packages.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected RHEL streams.
Prioritize systems using HTTP proxies with authenticated libsoup-based applications.
Avoid untrusted HTTP proxies for sensitive application traffic where operationally possible.
Review Red Hat guidance for RHEL 6, which is listed with unknown status.
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-319: 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-319 · source CWE mapping
Cleartext Transmission of Sensitive Information
Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.