FFmpeg through 9.0.2 Heap Buffer Overflow via PSD Decoder RLE Path
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects 32-bit FFmpeg builds (through 9.0.2). Crafted PSD image whose dimensions and channel counts have a product exceeding 4 GB.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
FFmpeg through 9.0.2 contains a heap buffer overflow vulnerability in the PSD decoder in libavcodec/psd.c that allows attackers to corrupt heap memory on 32-bit builds by supplying a crafted PSD image. Attackers can choose dimensions and channel counts whose product exceeds 4 GB, truncating the av_malloc allocation size so decode_rle() writes attacker-controlled data past the buffer, causing crashes or possible code execution.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.3/10CVSS 7.3
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects 32-bit FFmpeg builds (through 9.0.2). Crafted PSD image whose dimensions and channel counts have a product exceeding 4 GB.Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
through 9.0.2
Evidence 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125213
Is CVE-2026-125213 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted PSD image can make FFmpeg's PSD decoder write past the end of a heap buffer while handling its run-length encoded data. The memory corruption can crash the program or possibly allow code execution.Source: vulncheck.com
Which versions are affected by CVE-2026-125213?
FFmpeg: through 9.0.2.Source: cve.now feed data
Am I affected, and how do I check?
The facts name FFmpeg through 9.0.2 and 32-bit builds specifically. The bug needs a PSD image whose width, height and channel count multiply to more than 4 GB. To check a build, run ffmpeg -version and see whether it reports 9.0.2 or older and whether the build is 32-bit.Source: vulncheck.com
How do I fix CVE-2026-125213?
No fixed version is listed in the checked facts, so no upgrade target can be named from them. Check the FFmpeg project or your distributor for a patched release.Source: vulncheck.com