music-metadata: Uncontrolled memory allocation in APEv2 parser

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-107387: 0.19% estimated exploitation activity in the next 30 days; percentile 9.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary music-metadata 11.15.0 is vulnerable to uncontrolled memory allocation in the APEv2 parser. The parser reads the size of an APEv2 tag item from the input file and uses that value to allocate memory before checking whether the file actually contains that many bytes. A small crafted .ape file can declare a very large binary tag item, such as cover art, and force the parser to allocate a large buffer. This issue is specific to APEv2 parsing and is separate from the ID3v2, MP4, and EBML advisories. Affected component - lib/apev2/APEv2Token.ts - lib/apev2/APEv2Parser.ts The untrusted size is read here: It is later used directly for allocation when parsing binary tag items: The allocation happens before the parser confirms that the declared size fits inside the remaining file data. Impact An application that parses untrusted .ape files with music-metadata may be vulnerable to denial of service through memory exhaustion. The demonstrated payload is only 134 bytes but causes a 128…

Published by the source

8 Oct 2026, 19:43 UTC

Last modified by the source

8 Oct 2026, 20:00 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-53v6-4h7p-p4gj

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-53v6-4h7p-p4gj

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-53v6-4h7p-p4gj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107387

Advisory: music-metadata: Uncontrolled memory allocation in APEv2 parser
IDs: CVE-2026-107387, GHSA-53v6-4h7p-p4gj
Record: https://patchnext.com/advisories/cve-2026-107387 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: music-metadata 11.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm music-metadata: affected <= 11.12.3; fixed in 11.16.0

## Suggested inspection (read-only)
- `npm ls music-metadata --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on music-metadata.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-53v6-4h7p-p4gj (GitHub-reviewed advisory GHSA-53v6-4h7p-p4gj lists affected ranges: npm music-metadata >=0 <=11.12.3)
- Verified: https://osv.dev/vulnerability/GHSA-53v6-4h7p-p4gj (OSV record GHSA-53v6-4h7p-p4gj lists affected ranges: npm music-metadata >=0 <11.16.0 (fixed))

Commands are suggestions: review each one before running it.