CVE-2026-95121: CVE-2026-95121 is a high-severity
Source CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Until a patch is available, avoid processing untrusted MP4 files with mp4v2 2.0.0 to mitigate risk.
Description
CVE-2026-95121 is a high-severity vulnerability in mp4v2 version 2.0.0 where an attacker can execute arbitrary code by exploiting an unchecked offset subtraction in the MP4RtpAtom::ReadHntiType() function. This flaw allows a specially crafted MP4 file to trigger a near-2^64 allocation size, leading to potential memory corruption and code execution.
References
- github.com/TechSmith/mp4v2/issues/98 (opens in a new tab)
- github.com/TechSmith/mp4v2/pull/100 (opens in a new tab)
- github.com/TechSmith/mp4v2/pull/100/changes/c7f4e1da1b75996a053b05b69be8e738bf77a26c (opens in a new tab)
- gist.github.com/1820893135-pixel/c56b6a1627453e67ca2fb7e29bae95c6 (opens in a new tab)