CVE-2026-125069 json
FFmpeg through 9.0.2 NULL Pointer Dereference via Motion Pixels Decoder
published 2d ago modified yesterday also EUVD-2026-120244
- cvss
- 4.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
FFmpeg through 9.0.2 contains a NULL pointer dereference vulnerability in the Motion Pixels decoder because mp_decode_frame() ignores init_get_bits() failure. Attackers supplying a roughly 2^28-byte packet through the libavcodec API overflow the bit count, causing reads from a NULL buffer that crash the process.
Patch / fix
Is CVE-2026-125069 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.7 | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.7 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 5.7 | CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- FFmpeg FFmpeg
Classification
- Weakness
-
- CWE-252 Unchecked Return Value
References
-
github.com
/FFmpeg/FFmpeg/commit/26b4c37526fe0ecf1095b45daac08050f25f7659
patch
-
code.ffmpeg.org
/FFmpeg/FFmpeg/pulls/25704
issue-tracking
-
github.com
/FFmpeg/FFmpeg/blob/n9.0.2/libavcodec/motionpixels.c#L302
technical-description
-
github.com
/FFmpeg/FFmpeg
product
-
vulncheck.com
/advisories/ffmpeg-through-9.0.2-null-pointer-dereference-via-motion-pixels-decoder
third-party-advisory
Sources
- CVE List CVE-2026-125069
- NVD CVE-2026-125069
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.