Vulnerability in music-metadata (CVE-2026-107391)
Summary
Vulnerability in music-metadata (CVE-2026-107391). Risk of unauthorized operations or information disclosure. Exploitable via stsd. Mitigation: upgrade to 11.12.1 or later.
Original description
The description as published by the source.
Summary
StsdAtom.get() in lib/mp4/AtomToken.ts parses an MP4 stsd (sample description) box's entry table by advancing a cursor with off += size - 4, where size is a 32-bit, attacker-controlled per-entry length read straight from the file. When size == 0, that advance is 0, so a file declaring a huge entry_count and a first entry size of 0 spins forever: same bytes read every iteration, no progress, no exit. Because StsdAtom.get runs synchronously inside strtok3's tokenizer, this doesn't just fail slowly — it blocks the Node.js event loop entirely for the whole process. A 48-byte file is enough to hang any service that parses user-uploaded audio/video metadata through parseBuffer, parseFile, parseStream, parseBlob, or parseWebStream.
This is currently unreleased — present on the master branch only, not in the latest npm release (11.14.0) or any earlier one. Reporting now, before it ships.
Details
lib/mp4/AtomToken.ts, StsdAtom.get():
for (let n = 0; n < header.numberOfEntries; ++n) {
const size = Token.UINT32_BE.get(buf, off); // attacker-controlled entry size
off += Token.UINT32_BE.len; // +4 (skip the size field)
table.push(new SampleDescriptionTable(size - Token.UINT32_BE.len).get(buf, off));
off += size - Token.UINT32_BE.len; // net advance = size - 4
}
- Introduced by commit
d2a7d6f("fix(mp4): locate each sample entry after the first correctly", merged via PR #2…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107391 has been found in music-metadata.
Attackers can target a specific entry point like stsd over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.2/10.
What to do: upgrade music-metadata to 11.12.1 or later.
If unsure, ask your IT team or search "music-metadata CVE-2026-107391" on the vendor's site.
CVE-2026-107391 (music-metadata) — CWE-400 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: stsd / size / entry_count / StsdAtom.get
Patched: 11.12.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in music-metadata. Attackers reach the vulnerable code path via stsd without authentication.
Check the vendor advisory for the affected versions of music-metadata. Attack surface: stsd / size / entry_count / StsdAtom.get.
Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.
Update to 11.12.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'music-metadata' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'music-metadata' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
music-metadataを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade music-metadata to 11.12.1ステージング環境で 11.12.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- exploit security-advisories@github.com
- exploit security-advisories@github.com
- exploit security-advisories@github.com
- patch security-advisories@github.com
- web github.com