# CVE-2026-75144: FFmpeg Heap Buffer Overflow in VC-2/Dirac RTP Packetizer

> Attackers can trigger heap buffer overflow and potential code execution in FFmpeg by supplying crafted Dirac data units to the RTP packetizer.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-75144, ECHO-d43d-3438-b69f, GHSA-mg5r-49w7-j3cv, UBUNTU-CVE-2026-75144

## What is CVE-2026-75144?

CVE-2026-75144 is a high-severity memory corruption vulnerability in FFmpeg, published on 19 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

FFmpeg before commit 1cdeb3c contains a heap buffer overflow vulnerability in the VC-2/Dirac RTP packetizer (libavformat/rtpenc_vc2hq.c) that allows attackers to trigger memory corruption by supplying a crafted Dirac data unit. The packetizer copies an input-derived data unit or fragment size into a fixed-size buffer without an upper bound check, causing a heap buffer overflow when the crafted input is packetized for RTP output.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Apply the vendor's patch.

## Is CVE-2026-75144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75144 is a high-severity memory corruption vulnerability in FFmpeg, published on 19 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-75144 in the wild and no public exploit code.

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

## Sources

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

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