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

> A specially crafted MP4 file can cause an integer underflow in Bento4, leading to application termination and denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-p8mj-xj67-6v9f

## What is CVE-2026-88376?

CVE-2026-88376 is a high-severity vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bento4 1.6.0.0 contains an integer underflow vulnerability in AP4_AvccAtom::Create() and AP4_HvccAtom::Create(). A specially crafted MP4 file containing an avcC or hvcC atom with a declared size smaller than the atom header size can cause the payload-size calculation to wrap to a large unsigned value. The resulting invalid buffer allocation and copy operations can cause application termination, leading to denial of service.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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


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

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

## Is CVE-2026-88376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88376 is a high-severity vulnerability in n/a, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88376 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-88376/ (Markdown: https://insights.sbomify.com/CVE-2026-88376/index.md)
```

## Sources

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

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