CVE-2026-5119

HIGHNVD 8.25.9▼
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2026-03-30. NVD baseline CVSS 8.2; sources differ by 2.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
5.9(medium)
EPSS
16.7%
KEV
Not listed

Published

March 30, 2026

Last Modified

June 9, 2026

Advisory Details (5)

Auto-updated May 6, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available

(CVE-2026-5119) (#YWH-PGM9867-176) Cleartext Transmission of Sensitive Information on libsoup through soup_session.c::tunnel_connect() due to cookies being transmitted in cleartext in HTTP CONNECT request (#502) · Issues · GNOME / libsoup · GitLab

https://gitlab.gnome.org/GNOME/libsoup/-/issues/502
redhat Patch Available

2452932 – (CVE-2026-5119) CVE-2026-5119 libsoup: libsoup: Information disclosure via cleartext transmission of cookies during HTTPS tunnel establishment

Affected: Red Hat Enterprise Linux 9

https://bugzilla.redhat.com/show_bug.cgi?id=2452932
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-5119
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:14087
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:13978

Vendor Advisories for CVE-2026-5119(16)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibsoup-0:2.62.2-12.el7_92026-06-09redhat
redhatlibsoup-0:2.62.3-2.el8_6.92026-06-08redhat
redhatlibsoup-0:2.62.3-2.el8_4.92026-06-03redhat
redhatlibsoup-0:2.62.3-3.el8_8.92026-06-03redhat
redhatlibsoup-0:2.72.0-8.el9_2.112026-06-01redhat
redhatlibsoup-0:2.72.0-10.el9_6.72026-06-01redhat
redhatlibsoup-0:2.72.0-8.el9_4.102026-06-01redhat
redhatlibsoup-0:2.72.0-8.el9_0.102026-05-28redhat
redhatlibsoup3-0:3.6.5-3.el10_2.112026-05-19redhat
redhatlibsoup-0:2.72.0-16.el9_8.12026-05-19redhat
redhatlibsoup3-0:3.6.5-3.el10_0.152026-05-14redhat
redhatlibsoup3-0:3.6.5-3.el10_1.112026-05-11redhat
redhatlibsoup-0:2.62.3-14.el8_102026-05-06redhat
redhatlibsoup-0:2.72.0-12.el9_7.62026-05-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-19 19:26 UTCEPSS rescore
Show 61 more
  1. 2026-06-19 19:26 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-16 17:53 UTCEPSS rescore
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 23:18 UTCEPSS rescore
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-11 22:49 UTCEG score recompute
  13. 2026-06-11 22:49 UTCVendor advisory
  14. 2026-06-11 22:49 UTCGHSA enrichment
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-10 22:19 UTCEPSS rescore
  17. 2026-06-10 15:34 UTCEG score recompute
  18. 2026-06-10 15:34 UTCVendor advisory
  19. 2026-06-10 15:34 UTCGHSA enrichment
  20. 2026-06-10 13:22 UTCEPSS rescore
  21. 2026-06-09 15:16 UTCEG score recompute
  22. 2026-06-09 15:16 UTCVendor advisory
  23. 2026-06-09 15:16 UTCGHSA enrichment
  24. 2026-06-09 10:41 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  25. 2026-06-09 10:05 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
  26. 2026-06-08 23:31 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-08 13:07 UTCEG score recompute
  29. 2026-06-08 13:07 UTCVendor advisory
  30. 2026-06-08 13:07 UTCGHSA enrichment
  31. 2026-06-07 15:25 UTCEPSS rescore
  32. 2026-06-07 11:44 UTCEG score recompute
  33. 2026-06-07 11:44 UTCVendor advisory
  34. 2026-06-07 11:44 UTCGHSA enrichment
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-05 22:47 UTCEPSS rescore
  37. 2026-06-05 06:10 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-04 13:12 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-02 20:13 UTCEPSS rescore
  42. 2026-06-01 13:52 UTCEPSS rescore
  43. 2026-06-01 13:52 UTCEPSS rescore
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 00:16 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-29 13:44 UTCEPSS rescore
  49. 2026-05-29 13:44 UTCEPSS rescore
  50. 2026-05-28 13:44 UTCEPSS rescore
  51. 2026-05-28 13:44 UTCEPSS rescore
  52. 2026-05-27 13:40 UTCEPSS rescore
  53. 2026-05-27 13:40 UTCEPSS rescore
  54. 2026-05-26 13:44 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-21 22:43 UTCEPSS rescore
  57. 2026-05-20 22:38 UTCEPSS rescore
  58. 2026-05-20 19:57 UTCEG score recompute
  59. 2026-05-20 19:57 UTCVendor advisory
  60. 2026-05-20 19:57 UTCGHSA enrichment
  61. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5119?
CVE-2026-5119 is a high vulnerability published on March 30, 2026. 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…
When was CVE-2026-5119 disclosed?
CVE-2026-5119 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5119 actively exploited?
CVE-2026-5119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5119?
CVE-2026-5119 has a CVSS v3 base score of 8.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.9.
How do I remediate CVE-2026-5119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-5119

Explore →

Is Your Infrastructure Affected by CVE-2026-5119?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs