dbcve.org
Music MetadataApplication · Borewit

CVE-2026-32256

HIGH · 7.5 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 11.12.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
music-metadata is a metadata parser for audio and video media files. Prior to version 11.12.3, music-metadata's ASF parser (`parseExtensionObject()` in `lib/asf/AsfParser.ts:112-158`) enters an infinite loop when a sub-object inside the ASF Header Extension Object has `objectSize = 0`. Version 11.12.3 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The music-metadata library's ASF parser contains a denial-of-service vulnerability where `parseExtensionObject()` enters an infinite loop when processing ASF Header Extension Objects with sub-objects having `objectSize = 0`. This can be triggered by specially crafted ASF files, causing the parsing thread to hang indefinitely.

MitigationUpgrade music-metadata to version 11.12.3 or later. Since this is a library dependency, identify all projects using this library and update the dependency accordingly, then verify ASF parsing functionality still works correctly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Music MetadataApplication
Affected:< 11.12.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate music-metadata in your project dependencies
    Search your project for music-metadata: check package.json, requirements.txt, pom.xml, or similar dependency manifests. If using npm, run `npm list music-metadata` or check node_modules/music-metadata/package.json
    Affected if music-metadata appears in your dependencies
  2. Determine the installed version
    Read the version field from the music-metadata package definition (e.g., package.json, or run `npm list music-metadata --depth=0`). Compare it to the affected range: any version below 11.12.3 is vulnerable
    Affected if Installed version is lower than 11.12.3
  3. Identify ASF/WMA file processing in your code
    Search your codebase for calls to the music-metadata parser with ASF or WMA files. Look for file extensions .asf, .wma in file reads, or explicit parser selection for ASF format
    Affected if Your application parses ASF or WMA audio files using music-metadata
  4. Locate the vulnerable ASF parser code
    If you have the library source available locally (in node_modules/music-metadata), navigate to lib/asf/asf-parser.js and verify the parseExtensionObject function exists. The vulnerability is triggered when parsing ASF Header Extension Objects with objectSize=0
    Affected if The parseExtensionObject function in your ASF parser handles zero-size objects without exit conditions

You are affected if your project uses music-metadata version below 11.12.3 and processes ASF/WMA audio files with the library's ASF parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.12.3 or later
Fixed in 11.12.3
Interim mitigation

Upgrade music-metadata to version 11.12.3 or later. Since this is a library dependency, identify all projects using this library and update the dependency accordingly, then verify ASF parsing functionality still works correctly.

Recommended fix High confidence

11.12.3

  1. Update the music-metadata package to version 11.12.3 or later using your package manager (e.g., npm install [email protected] or yarn upgrade [email protected])
  2. Verify the update was successful by checking the installed version (e.g., npm list music-metadata)
  3. Test your application to ensure the upgrade does not break existing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Music Metadata Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32256 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data