GHSA-53v6-4h7p-p4gj: music-metadata (CVE-2026-107387)

Package	Ecosystem	Affected	Fixed in
music-metadata	npm	<11.16.0	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

Score	Rating	CVSS	Vector	Source
6.2	Medium	3.1	CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H	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

Sources

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.