# CVE-2026-85197: Libsoup: libsoup: heap use-after-free in libsoup http/2 client on_data_read() via goaway during body upload

> A heap use-after-free in libsoup's HTTP/2 client allows attackers to trigger memory corruption, potentially leading to code execution or information disclosure.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 22 Oct 2026
- **Also known as:** AZL-99915, DEBIAN-CVE-2026-85197, ECHO-6373-a6e1-b411, GHSA-pq26-x6qp-8qr7, RHSA-2026:82728, ROOT-OS-DEBIAN-13-CVE-2026-85197, UBUNTU-CVE-2026-85197

## What is CVE-2026-85197?

CVE-2026-85197 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-85197?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libsoup3` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.18 |
| `libsoup3-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.18 |
| `libsoup3-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.18 |
| `libsoup3-devel` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.18 |
| `libsoup3-doc` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:3.6.5-3.el10_0.18 |

## How do I fix CVE-2026-85197?

Apply the vendor's patch.

## Is CVE-2026-85197 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85197 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85197 and fix it if it is affected.

What it is: CVE-2026-85197 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85197 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85197/ (Markdown: https://insights.sbomify.com/CVE-2026-85197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85197
- OSV: https://osv.dev/vulnerability/CVE-2026-85197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85197/
Summaries are generated and may contain mistakes; the official description above is the record.