# music-metadata: uncatchable process crash parsing a crafted \`.dsf\` (residual of GHSA-v6c2-xwv6-8xf7)

Advisory record · `GHSA-8j4c-6x6g-rq3j`

- **Identifiers:** `GHSA-8j4c-6x6g-rq3j` · `CVE-2026-107392`
- **State:** Confirmed
- **Severity:** CVSS 6.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-248](https://cwe.mitre.org/data/definitions/248.html) · [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-248](https://agentprime.io/advisories/tag/cwe-248.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:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

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

## Machine-written summary

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

> GHSA-8j4c-6x6g-rq3j affects the npm package music-metadata before 11.15.0, and is fixed in 11.15.0. A crafted .dsf file (or any file starting with the DSD magic) with a small chunk size makes the DSF parser skip a chunk with an un-awaited call, so the resulting error is an unhandled rejection that crashes the Node process even when the caller uses try/catch. An attacker only needs to get such a file parsed, which is a denial-of-service risk. Upgrade to music-metadata 11.15.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.0036, the 29th percentile, on 5 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-8j4c-6x6g-rq3j)

## Sources

- [GitHub Advisory Database: GHSA-8j4c-6x6g-rq3j](https://github.com/advisories/GHSA-8j4c-6x6g-rq3j)
- [OSV: GHSA-8j4c-6x6g-rq3j](https://osv.dev/vulnerability/GHSA-8j4c-6x6g-rq3j)
- <https://github.com/Borewit/music-metadata/security/advisories/GHSA-8j4c-6x6g-rq3j>
- <https://github.com/Borewit/music-metadata/pull/2700>
- <https://github.com/Borewit/music-metadata/commit/e7fc27a96e789d41ece41fdac590fc7618274a41>
- <https://github.com/Borewit/music-metadata>
- <https://github.com/Borewit/music-metadata/releases/tag/v11.15.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-8j4c-6x6g-rq3j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8j4c-6x6g-rq3j/>. Everything for agents: <https://agentprime.io/llms.txt>.