# CVE-2026-7135: GPAC MP4Box box_code_base.c elng_box_read out-of-bounds

> A local attacker can trigger an out-of-bounds read in GPAC MP4Box via a crafted file, potentially causing crashes or leaking memory.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 27 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-7135, GHSA-75mr-r5qh-vfwp, UBUNTU-CVE-2026-7135

## What is CVE-2026-7135?

CVE-2026-7135 is a medium-severity memory corruption vulnerability in GPAC, published on 27 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in GPAC up to 26.03-DEV-rev105-g8f39a1eb3-master. Affected by this vulnerability is the function elng_box_read of the file src/isomedia/box_code_base.c of the component MP4Box. Performing a manipulation of the argument elng results in out-of-bounds read. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The patch is named cf6ac48c972eaaee2af270adc3f36615325deb3e. The affected component should be upgraded.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-7135 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7135 is a medium-severity memory corruption vulnerability in GPAC, published on 27 Apr 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-7135 exists.

Affected product: GPAC. 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-7135/ (Markdown: https://insights.sbomify.com/CVE-2026-7135/index.md)
```

## Sources

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

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