CVE-2026-2369

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-19) is not newer than that change (2026-11-05), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-13105 (ENISA EUVD) · GHSA-rm63-3cv3-qm5w (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 19, 2026

Last Modified

November 5, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: redhat.
Web page

(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
Red Hat

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
Red HatMentions a patch (unverified)

CVE-2026-2369 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibsoup2.4-doc (2.52.2-1ubuntu0.3+esm6) @ xenial2026-11-11ubuntu

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.

Affected Packages

(6 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
libsoup2.42.74.3-1 ... 2.74.3-9 (16 versions)
  • every version on: no fix on record
—
libsoup33.2.2-2 ... 3.8.0-3 (38 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
libsoup2.42.74.3-10.1, 2.74.3-11
  • every version on: no fix on record
—
libsoup33.6.5-3 ... 3.8.0-3 (11 versions)
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libsoup2.42.72.0-2 ... 2.74.3-9 (28 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libsoup33.6.5-3 ... 3.6.5-9 (7 versions)
  • every version up to 3.6.6-1: fixed in 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 18× in last 7d / 85× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 399 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 299 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-2369?
CVE-2026-2369 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-2369 was made public on February 11, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 19, 2026. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-2369 actively exploited?
CVE-2026-2369 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-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?
A fix for CVE-2026-2369 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2369 are linked in the Vendor Advisories panel on this page.

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.