# CVE-2026-112060: librtmp (RTMPDump) through 2.6 Heap Out-of-Bounds Write via AMF3_Decode

> Attackers can trigger heap memory corruption and leak data via malicious RTMP streams in librtmp, potentially leading to code execution.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-112060, ECHO-82ec-ae04-2010, GHSA-x953-qc42-3hqh, UBUNTU-CVE-2026-112060

## What is CVE-2026-112060?

CVE-2026-112060 is a medium-severity memory corruption vulnerability in RTMPDump librtmp, published on 18 Oct 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

librtmp in RTMPDump through 2.6 contains an out-of-bounds read and heap out-of-bounds write vulnerability because AMF3_Decode ignores AMF3 property decode failures. Malicious RTMP servers or man-in-the-middle attackers can send oversized AMF3 string lengths, and with the token option DecodeTEA corrupts heap memory and leaks heap bytes.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

No fix has been published for CVE-2026-112060 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112060 is a medium-severity memory corruption vulnerability in RTMPDump librtmp, published on 18 Oct 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-112060 exists.

Affected product: RTMPDump librtmp. 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-112060/ (Markdown: https://insights.sbomify.com/CVE-2026-112060/index.md)
```

## Sources

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

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