CVE-2026-125191 FFmpeg through 9.0.2 V4L2 M2M Decoder Deadlock via Reference Count Leak
Medium 5.7
Published
Updated
Check this codebase for CVE-2026-125191 and fix it if it is affected.
What it is: CVE-2026-125191 is a medium-severity vulnerability in FFmpeg, published on 9 Nov 2026.
Exploitation: There is no known exploitation of CVE-2026-125191 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-125191/ (Markdown: https://insights.sbomify.com/CVE-2026-125191/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-125191?
CVE-2026-125191 is a medium-severity vulnerability in FFmpeg, published on 9 Nov 2026.
Official description
FFmpeg through 9.0.2 contains a reference count leak in libavcodec/v4l2_buffers.c that allows attackers to deadlock the V4L2 mem2mem decoder on multi-plane capture formats. Attackers can supply crafted H.264, HEVC, or VP9 streams with resolution changes, making ff_v4l2_m2m_codec_reinit() wait forever and hang the decoding application.
Weakness: CWE-911
Which versions are affected by CVE-2026-125191?
How do I fix CVE-2026-125191?
No fix has been published for CVE-2026-125191 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-125191 being exploited?
There is no known exploitation of CVE-2026-125191 in the wild and no public exploit code.
Sources
Also known as GHSA-rq22-g63f-454x, UBUNTU-CVE-2026-125191.