Session hijacking via cleartext CONNECT cookies
Published Mar 30, 2026 · Updated Mar 30, 2026
Cleartext cookie transmission in libsoup on Red Hat Enterprise Linux allows man-in-the-middle attackers to hijack HTTPS sessions. The soup_session.c tunnel_connect() path attaches session cookies to the unencrypted HTTP CONNECT request before TLS begins. Exposure requires an application configured to tunnel HTTPS through an HTTP proxy; captured cookies enable session hijacking or impersonation.
Summary
What happened
Cleartext cookie transmission in libsoup on Red Hat Enterprise Linux allows man-in-the-middle attackers to hijack HTTPS sessions. The soup_session.c tunnel_connect() path attaches session cookies to the unencrypted HTTP CONNECT request before TLS begins. Exposure requires an application configured to tunnel HTTPS through an HTTP proxy; captured cookies enable session hijacking or impersonation.
The record
- CVE
- CVE-2026-5119
- Published
- Mar 30, 2026
- Updated
- Mar 30, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-319, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 30, 2026CVE publishedPublication date reported by the CVE source.
- Mar 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo