# CVE-2026-125269: FFmpeg through 9.0.2 Double Free via cbs_sei_delete_message in cbs_sei.c


- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jg49-h5w2-rr7x, UBUNTU-CVE-2026-125269

## What is CVE-2026-125269?

CVE-2026-125269 is a high-severity vulnerability in FFmpeg, published on 9 Nov 2026. 

### Official description

FFmpeg through 9.0.2 contains a double free vulnerability in libavcodec/cbs_sei.c where cbs_sei_delete_message() leaves a stale extension_data reference that ff_cbs_sei_add_message() reuses. Attackers can supply a crafted H.264 stream with a display orientation SEI message followed by payload extension data, processed by h264_metadata with display_orientation=insert, to corrupt heap memory.

Weakness: CWE-415 (Double Free)

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


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

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

## Is CVE-2026-125269 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125269 is a high-severity vulnerability in FFmpeg, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125269 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-125269/ (Markdown: https://insights.sbomify.com/CVE-2026-125269/index.md)
```

## Sources

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

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