# CVE-2026-112061: librtmp (RTMPDump) through 2.6 Heap Out-of-Bounds Read via AMFProp_Decode

> A malicious RTMP server can crash the client via a heap out-of-bounds read in librtmp's AMFProp_Decode function.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/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-112061, ECHO-a100-b1a0-1695, GHSA-m837-gfcx-6jp4, UBUNTU-CVE-2026-112061

## What is CVE-2026-112061?

CVE-2026-112061 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 (RTMPDump) through 2.6 contains a heap out-of-bounds read vulnerability in AMFProp_Decode that reads an AMF0 strict-array element count before checking that four bytes remain. A malicious RTMP server or man in the middle can send an AMF0 body ending with a strict-array type byte and fewer than four trailing bytes to crash the client.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-112061 being exploited?

There is no known exploitation of CVE-2026-112061 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112061 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: There is no known exploitation of CVE-2026-112061 in the wild and no public exploit code.

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-112061/ (Markdown: https://insights.sbomify.com/CVE-2026-112061/index.md)
```

## Sources

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

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