# music-metadata: MP4 stsd sample-entry size==0 causes a synchronous infinite loop (DoS) — unreleased regression on master

Advisory record · `GHSA-f94x-6692-553q`

- **Identifiers:** `GHSA-f94x-6692-553q` · `CVE-2026-107391`
- **State:** Confirmed
- **Severity:** CVSS 6.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-835](https://cwe.mitre.org/data/definitions/835.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Oct 2026, 19:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `music-metadata` (npm): affected `<11.16.0`; fixed in `11.16.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Affected: music-metadata versions below 11.16.0 on npm. The source says the bug exists only on the master branch and is not in the latest npm release (11.14.0) or earlier, and it is fixed in 11.16.0. An attacker who can supply a crafted 48-byte MP4 file to a parse call (for example through an upload) can make the MP4 stsd box parser loop forever, blocking the Node.js event loop with no authentication needed. Upgrade to music-metadata 11.16.0 or later.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.2 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0032, the 24th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f94x-6692-553q)

## Sources

- [GitHub Advisory Database: GHSA-f94x-6692-553q](https://github.com/advisories/GHSA-f94x-6692-553q)
- [OSV: GHSA-f94x-6692-553q](https://osv.dev/vulnerability/GHSA-f94x-6692-553q)
- <https://github.com/Borewit/music-metadata/security/advisories/GHSA-f94x-6692-553q>
- <https://github.com/Borewit/music-metadata/pull/2734>
- <https://github.com/Borewit/music-metadata/commit/90a7d52c69e921a0b019592d887acd97b1c8b8a5>
- <https://github.com/Borewit/music-metadata>
- <https://github.com/Borewit/music-metadata/releases/tag/v11.16.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f94x-6692-553q>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f94x-6692-553q/>. Everything for agents: <https://agentprime.io/llms.txt>.