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.
CVE-2026-2369
“—” 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% (35th 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-06-17), so it does not.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALmedium confidence
- EG Risk
- 56EG 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
- 35th
- 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-10-19). 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: 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.
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
June 17, 2026
Advisory Details (3)
Auto-updated Sep 16, 2026(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/4982439091 – (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=2439091CVE-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-2369Vendor 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 / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libsoup2.4-tests (2.74.2-3ubuntu0.7) @ jammy | 2026-10-19 | ubuntu |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libsoup2.4 | 2.74.3-1 ... 2.74.3-9 (16 versions) |
| — |
| libsoup3 | 3.2.2-2 ... 3.6.6-1 (35 versions) |
| — |
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libsoup2.4 | 2.74.3-10.1, 2.74.3-11 |
| — |
| libsoup3 | 3.6.5-3 ... 3.6.6-1 (8 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libsoup2.4 | 2.72.0-2 ... 2.74.3-9 (28 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libsoup3 | 3.6.5-3 ... 3.6.5-9 (7 versions) |
| — |
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 24× in last 7d / 49× 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 it from the CNA feed. 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). Most recent first.
Showing the most recent 95 of 299 refreshes 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 204 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-19 18:17 UTCEG score recompute
- 2026-10-19 18:17 UTCVendor advisory
- 2026-10-19 18:17 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 18:35 UTCEG score recompute
- 2026-10-18 18:35 UTCVendor advisory
- 2026-10-18 18:35 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-18 03:54 UTCEG score recompute
- 2026-10-17 18:51 UTCEG score recompute
- 2026-10-17 18:51 UTCVendor advisory
- 2026-10-17 18:51 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-16 19:07 UTCEG score recompute
- 2026-10-16 19:07 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:19 UTCEG score recompute
- 2026-10-15 16:19 UTCVendor advisory
- 2026-10-15 16:19 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 10:25 UTCEG score recompute
- 2026-10-14 10:25 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-13 08:58 UTCEG score recompute
Show 70 moreShow fewer
- 2026-10-13 08:58 UTCVendor advisory
- 2026-10-13 08:57 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 16:21 UTCEG score recompute
- 2026-10-12 09:15 UTCVendor advisory
- 2026-10-12 09:15 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-10-11 20:03 UTCEG score recompute
- 2026-10-11 17:16 UTCEG score recompute
- 2026-10-11 14:47 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-16 11:11 UTCEG score recompute
- 2026-08-16 11:11 UTCVendor advisory
- 2026-08-16 11:11 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-08-15 00:21 UTCVendor advisory
- 2026-08-15 00:21 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-14 20:06 UTCVendor advisory
- 2026-08-14 20:06 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-14 15:51 UTCVendor advisory
- 2026-08-14 15:51 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-14 11:35 UTCVendor advisory
- 2026-08-14 11:35 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-14 07:21 UTCEG score recompute
- 2026-08-14 07:21 UTCVendor advisory
- 2026-08-14 07:21 UTCGHSA enrichmentGHSA-rm63-3cv3-qm5w · GitHub CVSS 6.5
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:11:libsoup2.4
Frequently asked(5)
What is CVE-2026-2369?
When was CVE-2026-2369 made public?
Is CVE-2026-2369 actively exploited?
What is the CVSS score of CVE-2026-2369?
How do I remediate CVE-2026-2369?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2369
Is Your Infrastructure Affected by CVE-2026-2369?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.