# CVE-2026-107390: music-metadata: MP4 parser allows memory exhaustion via oversized extended atom length

> An attacker can cause denial of service in applications parsing untrusted MP4 files by triggering memory exhaustion via oversized atom lengths.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-qc8q-pw95-mq6c

## What is CVE-2026-107390?

CVE-2026-107390 is a medium-severity denial of service vulnerability in Borewit music-metadata, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

music-metadata is a metadata parser for audio and video media files. Prior to 11.16.0, the MP4 parser accepts an attacker-controlled 64-bit extended atom size, converts it to a JavaScript Number, and uses the resulting payload length for atom-specific readToken calls before proving that the atom fits within its parent or the available input. A tiny MP4-family file can route an oversized length into payload parsing for atoms including mvhd, stsd, stsz, and date, causing a large allocation attempt or process failure before end-of-input validation. Applications that parse untrusted MP4-family media can therefore be denied service. This issue is fixed in version 11.16.0.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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

It affects 1 product.


Products: Borewit Music-Metadata.

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

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

## Is CVE-2026-107390 being exploited?

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

## Other vulnerabilities in Borewit music-metadata

- [CVE-2026-32256](https://insights.sbomify.com/CVE-2026-32256/): music-metadata has an infinite loop vulnerability in ASF parser (high 7.5)
- [CVE-2026-107387](https://insights.sbomify.com/CVE-2026-107387/): music-metadata: Uncontrolled memory allocation in APEv2 parser (medium 6.2)
- [CVE-2026-107388](https://insights.sbomify.com/CVE-2026-107388/): music-metadata: ID3v2 tag size not validated before allocation, causing memory exhaustion DoS (medium 6.2)
- [CVE-2026-107389](https://insights.sbomify.com/CVE-2026-107389/): music-metadata: EBML parser trusts element lengths, allowing memory exhaustion or process abort (medium 6.2)
- [CVE-2026-107391](https://insights.sbomify.com/CVE-2026-107391/): music-metadata: MP4 stsd sample-entry size==0 causes a synchronous infinite loop (DoS) — unreleased regression on master (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107390 is a medium-severity denial of service vulnerability in Borewit music-metadata, published on 8 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-107390 exists.

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

## Sources

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

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