A flaw was found in libsoup. A malicious HTTP/2 server or a Man-in-the-Middle (MITM) attacker can exploit a heap use-after-free vulnerability in the HTTP/2 client implementation. This occurs when a GNOME application uploads a file using HTTP/2, and the server sends a GOAWAY frame while the file body is being read asynchronously. This can lead to memory corruption, potentially resulting in information disclosure or arbitrary code execution.
CVE-2026-85197
Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-04. a secondary CVSS source baseline 7.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.6
- EG Score
- 7.6(high)
- EG Risk
- 50(Track)EG Risk 50/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 computedSeverity76% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
September 4, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 4, 20262528425 – (CVE-2026-85197) CVE-2026-85197 libsoup: libsoup: Heap use-after-free in libsoup HTTP/2 client on_data_read() via GOAWAY during body upload
https://bugzilla.redhat.com/show_bug.cgi?id=2528425CVE-2026-85197 - 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-85197Vendor Advisories for CVE-2026-85197(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-85197Microsoft Security Response Center (MSRC)High
Libsoup: libsoup: heap use-after-free in libsoup http/2 client on_data_read() via goaway during body upload
- GHSA-pq26-x6qp-8qr7GitHub Security AdvisoriesHigh
A flaw was found in libsoup. A malicious HTTP/2 server or a Man-in-the-Middle (MITM) attacker can...
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libsoup3-0:3.6.5-3.el10_2.14 | 2026-09-16 | redhat |
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
(5 across 3 ecosystems)
Debian:12(2)
| Package | Vulnerable range | Fixed in | 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 | Fixed in | Dependents |
|---|---|---|---|
| libsoup2.4 | 2.74.3-10.1, 2.74.3-11 | — | — |
| libsoup3 | 3.6.5-3 ... 3.6.6-1 (8 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libsoup3 | 3.6.5-3 ... 3.6.6-1 (8 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 44× in last 7d / 87× 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.
- 2026-09-19 06:05 UTCEG score recompute
- 2026-09-19 06:05 UTCVendor advisory
- 2026-09-19 06:05 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:52 UTCVendor advisory
- 2026-09-18 18:52 UTCGHSA enrichment
- 2026-09-18 07:39 UTCVendor advisory
- 2026-09-18 07:39 UTCGHSA enrichment
- 2026-09-17 20:26 UTCEG score recompute
- 2026-09-17 20:26 UTCVendor advisory
- 2026-09-17 20:26 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-17 05:44 UTCVendor advisory
- 2026-09-17 05:44 UTCGHSA enrichment
- 2026-09-16 18:27 UTCEG score recompute
- 2026-09-16 18:27 UTCVendor advisory
- 2026-09-16 18:27 UTCGHSA enrichment
- 2026-09-16 17:52 UTCEG score recompute
- 2026-09-16 17:52 UTCVendor advisory
- 2026-09-16 17:52 UTCGHSA enrichment
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 07:26 UTCEG score recompute
- 2026-09-16 07:26 UTCVendor advisory
- 2026-09-16 07:26 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
Show 62 moreShow fewer
- 2026-09-15 20:13 UTCVendor advisory
- 2026-09-15 20:13 UTCGHSA enrichment
- 2026-09-15 09:00 UTCEG score recompute
- 2026-09-15 09:00 UTCVendor advisory
- 2026-09-15 09:00 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 21:47 UTCVendor advisory
- 2026-09-14 21:47 UTCGHSA enrichment
- 2026-09-14 10:34 UTCVendor advisory
- 2026-09-14 10:34 UTCGHSA enrichment
- 2026-09-13 23:19 UTCEG score recompute
- 2026-09-13 23:19 UTCVendor advisory
- 2026-09-13 23:19 UTCGHSA enrichment
- 2026-09-13 12:07 UTCVendor advisory
- 2026-09-13 12:07 UTCGHSA enrichment
- 2026-09-13 00:54 UTCEG score recompute
- 2026-09-13 00:54 UTCVendor advisory
- 2026-09-13 00:54 UTCGHSA enrichment
- 2026-09-12 13:41 UTCVendor advisory
- 2026-09-12 13:41 UTCGHSA enrichment
- 2026-09-12 02:28 UTCVendor advisory
- 2026-09-12 02:28 UTCGHSA enrichment
- 2026-09-11 15:16 UTCEG score recompute
- 2026-09-11 15:16 UTCVendor advisory
- 2026-09-11 15:16 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 04:02 UTCGHSA enrichment
- 2026-09-10 16:50 UTCEG score recompute
- 2026-09-10 16:50 UTCGHSA enrichment
- 2026-09-10 05:37 UTCGHSA enrichment
- 2026-09-09 18:24 UTCVendor advisory
- 2026-09-09 18:24 UTCGHSA enrichment
- 2026-09-09 07:10 UTCEG score recompute
- 2026-09-09 07:10 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 19:58 UTCGHSA enrichment
- 2026-09-08 13:17 UTCGHSA enrichment
- 2026-09-08 02:03 UTCEG score recompute
- 2026-09-08 02:02 UTCGHSA enrichment
- 2026-09-07 14:49 UTCGHSA enrichment
- 2026-09-07 03:35 UTCGHSA enrichment
- 2026-09-06 16:21 UTCEG score recompute
- 2026-09-06 16:21 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 05:08 UTCGHSA enrichment
- 2026-09-05 17:55 UTCEG score recompute
- 2026-09-05 17:55 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 06:41 UTCGHSA enrichment
- 2026-09-04 19:19 UTCEG score recompute
- 2026-09-04 19:19 UTCGHSA enrichment
- 2026-09-04 18:40 UTCEG score recompute
- 2026-09-04 18:40 UTCGHSA enrichment
- 2026-09-04 15:26 UTCEG score recompute
- 2026-09-04 15:26 UTCGHSA enrichment
- 2026-09-04 14:49 UTCEG score recompute
- 2026-09-04 14:49 UTCGHSA enrichment
- 2026-09-04 08:29 UTCEG score recompute
- 2026-09-04 07:44 UTCEG score recompute
- 2026-09-04 07:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-85197?
When was CVE-2026-85197 disclosed?
Is CVE-2026-85197 actively exploited?
What is the CVSS score of CVE-2026-85197?
How do I remediate CVE-2026-85197?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-85197
Is Your Infrastructure Affected by CVE-2026-85197?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.