# CVE-2026-107387: music-metadata: Uncontrolled memory allocation in APEv2 parser

> An attacker can cause memory exhaustion and denial of service by providing a crafted APEv2 audio file to the music-metadata library.

- **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:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-53v6-4h7p-p4gj, MINI-7qrm-rw5j-7hwq

## What is CVE-2026-107387?

CVE-2026-107387 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 APEv2 parser reads an attacker-controlled tag-item size and allocates a Uint8Array for a binary item before proving that the declared item fits in the remaining tag or file data. A small crafted APE file can therefore trigger a disproportionate allocation, including through cover-art items, and repeated or concurrent parsing can exhaust process memory. The demonstrated impact is availability loss only. 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-107387?

2 open source packages ship an affected version, including music-metadata. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `music-metadata` | npm | All versions | 11.16.0 |
| `music-metadata` | npm | All versions | 11.16.0 |

Products: Borewit Music-Metadata.

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

Upgrade music-metadata to 11.16.0 or later.

## Is CVE-2026-107387 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107387 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-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-107390](https://insights.sbomify.com/CVE-2026-107390/): music-metadata: MP4 parser allows memory exhaustion via oversized extended atom length (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-107387 and fix it if it is affected.

What it is: CVE-2026-107387 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-107387 exists.

Affected packages and fixed versions:
- music-metadata (npm): affected all versions; fixed in 11.16.0
- music-metadata (npm): affected all versions; fixed in 11.16.0

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

## Sources

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

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