Vulnerability in music-metadata (CVE-2026-107389)
Summary
Vulnerability in music-metadata (CVE-2026-107389). Risk of unauthorized operations or information disclosure. Exploitable via Uint8Array. Mitigation: upgrade to 11.16.0 or later.
Original description
The description as published by the source.
Summary
The Matroska/WebM EBML parser decodes attacker-controlled variable-length integer (VINT) element lengths without first validating that the declared element fits within its enclosing container or the available input. Leaf lengths are then used directly for string-token and Uint8Array allocations.
A very small crafted .webm, .mkv, or .mka file can therefore cause a disproportionately large allocation, an out-of-memory denial of service, or—in one demonstrated parseFile case—an uncatchable V8 fatal abort.
Impact
Applications that parse untrusted Matroska/WebM media can be denied service. Depending on the input, parser API, and Node.js/V8 version, the demonstrated outcomes include:
- a 34-byte input causing an approximately 128 MiB allocation before end-of-input;
- a 70-byte input causing a 500 MiB allocation through a binary EBML leaf, with concurrent parses multiplying memory consumption;
- a 48-byte file causing an uncatchable V8 fatal abort through
parseFilewhen a leaf declares a length of 32 GiB.
The fatal-abort case was reproduced on music-metadata 11.15.0 with Node.js 26.7.0. It was deterministic across three runs and exited with code 133 despite a surrounding try/catch. The same reporter did not reproduce that fatal abort through parseBuffer on Node.js 20 through 25; those configurations can still encounter allocation attempts or catchable errors. The exact failure mode is therefore runtime- and tokenizer-dependent, but the underly…
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-107389 has been found in music-metadata.
Attackers can target a specific entry point like Uint8Array 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.16.0 or later.
If unsure, ask your IT team or search "music-metadata CVE-2026-107389" on the vendor's site.
CVE-2026-107389 (music-metadata) — CWE-789 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: Uint8Array / parseFile / try / catch
Patched: 11.16.0 — 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-789) exists in music-metadata. Attackers reach the vulnerable code path via Uint8Array without authentication.
Check the vendor advisory for the affected versions of music-metadata. Attack surface: Uint8Array / parseFile / try / catch.
Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.
Update to 11.16.0.
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.16.0ステージング環境で 11.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。