CVE-2026-2369

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in libsoup. An integer underflow vulnerability occurs when processing content with a zero-length resource, leading to a buffer overread. This can allow an attacker to potentially access sensitive information or cause an application level denial of service.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

March 19, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Patch available. Sources: redhat.
generic

(CVE-2026-2369) Integer underflow in CVE-2025-32052 fix when resource_length=0 (#498) · Issues · GNOME / libsoup · GitLab

https://gitlab.gnome.org/GNOME/libsoup/-/issues/498
redhat

2439091 – (CVE-2026-2369) CVE-2026-2369 libsoup: libsoup: Buffer overread due to integer underflow when handling zero-length resources

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-2369

Vendor Advisories for CVE-2026-2369(1)

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

Affected Packages

(6 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
libsoup2.42.74.3-1 ... 2.74.3-9 (16 versions)——
libsoup33.2.2-2 ... 3.6.6-1 (35 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
libsoup2.42.74.3-10.1, 2.74.3-11——
libsoup33.6.5-3 ... 3.6.6-1 (8 versions)——
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libsoup2.42.72.0-2 ... 2.74.3-9 (28 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libsoup33.6.5-3 ... 3.6.5-9 (7 versions)3.6.6-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 90× 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.

Showing the most recent 100 of 241 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:11 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-09-01 04:39 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-24 14:17 UTCEPSS rescore
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:11 UTCEG score recompute
  22. 2026-08-16 11:11 UTCVendor advisory
  23. 2026-08-16 11:11 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 00:21 UTCVendor advisory
  2. 2026-08-15 00:21 UTCGHSA enrichment
  3. 2026-08-14 20:06 UTCVendor advisory
  4. 2026-08-14 20:06 UTCGHSA enrichment
  5. 2026-08-14 15:51 UTCVendor advisory
  6. 2026-08-14 15:51 UTCGHSA enrichment
  7. 2026-08-14 11:35 UTCVendor advisory
  8. 2026-08-14 11:35 UTCGHSA enrichment
  9. 2026-08-14 07:21 UTCEG score recompute
  10. 2026-08-14 07:21 UTCVendor advisory
  11. 2026-08-14 07:21 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 02:20 UTCVendor advisory
  14. 2026-08-13 02:20 UTCGHSA enrichment
  15. 2026-08-12 22:05 UTCEG score recompute
  16. 2026-08-12 22:05 UTCVendor advisory
  17. 2026-08-12 22:05 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-12 01:44 UTCVendor advisory
  20. 2026-08-12 01:44 UTCGHSA enrichment
  21. 2026-08-11 21:28 UTCEG score recompute
  22. 2026-08-11 21:28 UTCVendor advisory
  23. 2026-08-11 21:28 UTCGHSA enrichment
  24. 2026-08-11 13:42 UTCEPSS rescore
  25. 2026-08-11 08:47 UTCVendor advisory
  26. 2026-08-11 08:47 UTCGHSA enrichment
  27. 2026-08-11 04:32 UTCEG score recompute
  28. 2026-08-11 04:32 UTCVendor advisory
  29. 2026-08-11 04:32 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 12:14 UTCVendor advisory
  32. 2026-08-10 12:14 UTCGHSA enrichment
  33. 2026-08-10 06:27 UTCVendor advisory
  34. 2026-08-10 06:27 UTCGHSA enrichment
  35. 2026-08-10 02:08 UTCVendor advisory
  36. 2026-08-10 02:08 UTCGHSA enrichment
  37. 2026-08-09 21:53 UTCVendor advisory
  38. 2026-08-09 21:53 UTCGHSA enrichment
  39. 2026-08-09 17:37 UTCEG score recompute
  40. 2026-08-09 17:37 UTCVendor advisory
  41. 2026-08-09 17:37 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 13:22 UTCVendor advisory
  44. 2026-08-09 13:22 UTCGHSA enrichment
  45. 2026-08-09 06:54 UTCEG score recompute
  46. 2026-08-09 06:54 UTCVendor advisory
  47. 2026-08-09 06:54 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 10:25 UTCVendor advisory
  50. 2026-08-08 10:25 UTCGHSA enrichment
  51. 2026-08-08 06:10 UTCVendor advisory
  52. 2026-08-08 06:10 UTCGHSA enrichment
  53. 2026-08-08 01:55 UTCVendor advisory
  54. 2026-08-08 01:55 UTCGHSA enrichment
  55. 2026-08-07 21:39 UTCVendor advisory
  56. 2026-08-07 21:39 UTCGHSA enrichment
  57. 2026-08-07 17:24 UTCEG score recompute
  58. 2026-08-07 17:24 UTCVendor advisory
  59. 2026-08-07 17:24 UTCGHSA enrichment
  60. 2026-08-06 19:26 UTCEG score recompute
  61. 2026-08-06 19:26 UTCVendor advisory
  62. 2026-08-06 19:26 UTCGHSA enrichment
  63. 2026-08-06 13:46 UTCEPSS rescore
  64. 2026-08-06 10:28 UTCVendor advisory
  65. 2026-08-06 10:28 UTCGHSA enrichment
  66. 2026-08-06 05:49 UTCVendor advisory
  67. 2026-08-06 05:49 UTCGHSA enrichment
  68. 2026-08-06 01:34 UTCEG score recompute
  69. 2026-08-06 01:34 UTCVendor advisory
  70. 2026-08-06 01:34 UTCGHSA enrichment
  71. 2026-08-05 19:17 UTCEPSS rescore
  72. 2026-08-04 15:10 UTCEPSS rescore
  73. 2026-08-04 04:58 UTCVendor advisory
  74. 2026-08-04 04:58 UTCGHSA enrichment
  75. 2026-08-04 00:43 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-2369?
CVE-2026-2369 is a critical vulnerability published on March 19, 2026. A flaw was found in libsoup. An integer underflow vulnerability occurs when processing content with a zero-length resource, leading to a buffer overread. This can allow an attacker to potentially access sensitive information or cause an application level denial of service.
When was CVE-2026-2369 disclosed?
CVE-2026-2369 was first published in the National Vulnerability Database on March 19, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2369 actively exploited?
CVE-2026-2369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.9% of all scored CVEs.
What is the CVSS score of CVE-2026-2369?
CVE-2026-2369 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-2369?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2369, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2369

Explore →

Is Your Infrastructure Affected by CVE-2026-2369?

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

Start Free Scan →Browse All CVEs