FFmpeg 5.0 through 9.0.2 Path Traversal via IMF Demuxer ASSETMAP Path
Affects FFmpeg 5.0 through 9.0.2 when the IMF demuxer processes ASSETMAP Path values from packages. No vendor severity rating or fixed version is listed in the checked facts.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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, a widely used multimedia framework, is affected through its IMF (Interoperable Master Format) demuxer. An attacker who supplies a specially crafted IMF package can make FFmpeg open files outside that package, potentially reading local media files, revealing whether files exist and their sizes, or triggering requests to other systems.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
FFmpeg 5.0 through 9.0.2 contains a path traversal vulnerability in the IMF demuxer that allows attackers to open files outside the package via unvalidated ASSETMAP Path elements. Attackers can supply a crafted IMF package with '..' or absolute paths to demux local MXF files, probe file existence and size, or trigger server-side requests.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- FFmpeg FFmpeg
From 5.0 · through 9.0.2
References 4
code.ffmpeg.org
GitHub · FFmpeg/FFmpeg
Questions about CVE-2026-120210
What does this mean?
The IMF demuxer accepts ASSETMAP Path values that can point outside the package directory, which is a path traversal flaw. The fix described in the source rejects asset map paths that leave the package directory.Source: code.ffmpeg.org
Am I affected, and how do I check?
FFmpeg versions 5.0 through 9.0.2 are in range, in setups where the IMF demuxer (libavformat/imfdec.c) reads ASSETMAP Path values from a package. To check a version, run ffmpeg -version and compare it with that range.Source: code.ffmpeg.org
What should I do about it?
The checked facts do not name a fixed release, so no upgrade target can be given from them. Check the FFmpeg project's advisory or release notes for the first version that includes the fix.Source: code.ffmpeg.org
Is it 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 if there's no patch?
The checked facts do not list a workaround. Limiting the IMF demuxer to packages from trusted sources would reduce exposure to the affected code path until a fixed version is installed.Source: code.ffmpeg.org