# music-metadata: Uncontrolled memory allocation in APEv2 parser Advisory record · `GHSA-53v6-4h7p-p4gj` - **Identifiers:** `GHSA-53v6-4h7p-p4gj` · `CVE-2026-107387` - **State:** Confirmed - **Severity:** CVSS 6.2 Medium - **Critical:** No - **Weakness (CWE):** [CWE-789](https://cwe.mitre.org/data/definitions/789.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. > GHSA-53v6-4h7p-p4gj affects the npm package music-metadata versions below 11.16.0, with 11.16.0 listed as the fixed release. The APEv2 parser reads a tag item size from the file and allocates memory for it before checking that the file holds that many bytes, so a small crafted .ape file can force a large allocation, with the source describing a 128 MiB example. An attacker only needs to get an application to parse the malicious file, and the impact is memory exhaustion denial of service; no confidentiality or integrity impact is reported. 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.0019, the 9th percentile, on 12 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-53v6-4h7p-p4gj) ## Sources - [GitHub Advisory Database: GHSA-53v6-4h7p-p4gj](https://github.com/advisories/GHSA-53v6-4h7p-p4gj) - [OSV: GHSA-53v6-4h7p-p4gj](https://osv.dev/vulnerability/GHSA-53v6-4h7p-p4gj) - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .