CVE-2026-52295 Memory corruption in FFmpeg

Low 2.9 Published Updated

An out-of-bounds read in FFmpeg's IAMF writer allows attackers to cause crashes or leak memory contents via crafted media files.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-52295?

CVE-2026-52295 is a low-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 1 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

FFmpeg before 9.0 has an out-of-bounds read because the copied extradata lacked required padding before GetBitContext-based access in libavformat/iamf_writer.c.

Weakness: CWE-120, CWE-125

Which versions are affected by CVE-2026-52295?

It affects 1 product.

Products include Ffmpeg Ffmpeg.

How do I fix CVE-2026-52295?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-52295 being exploited?

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

All Ffmpeg Ffmpeg vulnerabilities

Sources

Also known as DEBIAN-CVE-2026-52295, GHSA-53pf-4457-qg7g, UBUNTU-CVE-2026-52295.

Is CVE-2026-52295 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free