Categories
CVE-2026-107387 medium CVSS 6.2

Vulnerability in music-metadata (CVE-2026-107387)

Summary

Vulnerability in music-metadata (CVE-2026-107387). Risk of unauthorized operations or information disclosure. Exploitable via tagItemHeader.size. Mitigation: upgrade to 11.16.0 or later.

Original description

The description as published by the source.

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:

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.

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:

npm install --ignore-scripts
n…

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-107387 has been found in music-metadata.
Attackers can target a specific entry point like tagItemHeader.size 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-107387" on the vendor's site.

CVE-2026-107387 (music-metadata) — CWE-789 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Attack surface: tagItemHeader.size
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.

❓ What is the problem

A vulnerability (CWE-789) exists in music-metadata. Attackers reach the vulnerable code path via tagItemHeader.size without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of music-metadata. Attack surface: tagItemHeader.size.

🔥 Severity

Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 11.16.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'music-metadata' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で music-metadata を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade music-metadata to 11.16.0

    ステージング環境で 11.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm music-metadata
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"11.16.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details