Skip to main content
← Vulnerabilities

FFmpeg through 9.0.2 NULL Pointer Dereference via Motion Pixels Decoder

5.7MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Published
Last modified
6/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The FFmpeg libavcodec library, through version 9.0.2 (version numbers omitted here), has a NULL pointer dereference in its Motion Pixels decoder that can crash the process. An attacker who can reach the decoder locally, without logging in, but only if a user takes some action, can supply an oversized packet to crash the program; the bug does not give them access to data or control over the system.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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.

cve.now Index

6Pcve.now Index 6 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.7/10CVSS 5.7
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • FFmpeg FFmpeg

    through 9.0.2

Evidence 5

  1. Patch
  2. Report
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125069

Is CVE-2026-125069 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

Which versions are affected by CVE-2026-125069?

FFmpeg: through 9.0.2.Source: cve.now feed data