# CVE-2026-132754: MediaInfoLib before 26.10 Out-of-Bounds Read via File_Mpeg4::meta_iloc


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-7fhq-45g4-wv67, UBUNTU-CVE-2026-132754

## What is CVE-2026-132754?

CVE-2026-132754 is a medium-severity vulnerability in MediaArea MediaInfoLib, published on 18 Nov 2026. 

### Official description

MediaInfoLib before 26.10 contains an out-of-bounds read vulnerability in File_Mpeg4::meta_iloc that allows attackers to trigger a global buffer over-read via oversized iloc field sizes. Attackers can supply a crafted MP4 file with invalid offset_size or length_size values to overrun the BitStream_Fast mask table and crash applications analysing the file.

Weakness: CWE-125 (Out-of-bounds Read)

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

1 open source package ship an affected version, including mediaarea/mediainfolib.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `mediaarea/mediainfolib` | GitHub | `pkg:github/mediaarea/mediainfolib` | All versions | 26.10 |

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

Upgrade mediaarea/mediainfolib to 26.10 or later.

## Is CVE-2026-132754 being exploited?

There is no known exploitation of CVE-2026-132754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132754 is a medium-severity vulnerability in MediaArea MediaInfoLib, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132754 in the wild and no public exploit code.

Affected packages and fixed versions:
- mediaarea/mediainfolib (GitHub): affected all versions; fixed in 26.10

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

## Sources

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

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