# CVE-2026-95121: Integer overflow in n/a

> An attacker can execute arbitrary code by providing a specially crafted MP4 file that triggers an integer overflow in the mp4v2 library.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-6cvh-jwvc-xjw2, UBUNTU-CVE-2026-95121

## What is CVE-2026-95121?

CVE-2026-95121 is a high-severity vulnerability in n/a, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in mp4v2 2.0.0 allows an attacker to execute arbitrary code via the MP4RtpAtom::ReadHntiType() in src/atom_rtp.cpp. A specially crafted MP4 file can cause an undersized rtp atom to produce a near-2^64 allocation size through an unchecked offset subtraction

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-95121?


## How do I fix CVE-2026-95121?

No fix has been published for CVE-2026-95121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95121 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95121 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95121 and fix it if it is affected.

What it is: CVE-2026-95121 is a high-severity vulnerability in n/a, published on 13 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95121 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95121/ (Markdown: https://insights.sbomify.com/CVE-2026-95121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95121
- OSV: https://osv.dev/vulnerability/CVE-2026-95121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95121/
Summaries are generated and may contain mistakes; the official description above is the record.