CVE Intelligence
Medium File handling

CVE-2026-120210 — FFmpeg 5.0 through 9.0.2 Path Traversal via IMF Demuxer ASSETMAP Path

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.

Published Oct 31, 2026 · Updated Oct 31, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Ffmpeg
Ffmpeg
CVSS base
4.3
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Ffmpeg Ffmpeg).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Ffmpeg Ffmpeg ≥ 5.0 and ≤ 9.0.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
5.3 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
4.3 CVSS 3.1 Medium 2.8 1.4 disclosure@vulncheck.com via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · ffmpeg/ffmpeg
    Oct 31, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 31, 2026
  • CVSS changed · 4.3
    Oct 31, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 31, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 31, 2026 · Alertas do Telegram
  • CVE published
    Oct 31, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 31, 2026 – Oct 31, 2026
  • 1× Official description updated · Oct 31, 2026 – Oct 31, 2026

References

4 on the record

Elsewhere on this site

Ffmpeg
every CVE for this vendor
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-107696 FFmpeg through 9.0.2 Infinite Loop via RTSP Redirect Handling in rtsp.c 23d
  • Medium CVE-2026-107698 FFmpeg before 7.1.4 and 8.0.2 SSRF via RTSP Redirect Handling 23d
  • Medium CVE-2026-107697 FFmpeg before 8.1.3 HLS Demuxer Security Check Bypass via parse_playlist() 23d
  • Medium CVE-2026-107695 FFmpeg before 8.1.3 HLS Demuxer Infinite Loop via Self-Referencing Playlist 23d
  • Low CVE-2026-107676 FFmpeg through 9.0.2 Uninitialized Memory Disclosure via HDR10+ Metadata Serializer 23d
  • Medium CVE-2026-107678 FFmpeg through 9.0.2 Stack Exhaustion via Recursive Free of pssh Boxes 23d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-120210 is "FFmpeg 5.0 through 9.0.2 Path Traversal via IMF Demuxer ASSETMAP Path", rated Medium. It affects Ffmpeg (Ffmpeg); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.