Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

music-metadata has an infinite loop vulnerability in ASF parser

CVE-2026-32256GHSA-v6c2-xwv6-8xf7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (music-metadata 11.12.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-32256: 0.41% estimated exploitation activity in the next 30 days; percentile 35.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Root Cause When objectSize is 0: 1. remaining = 0 - 24 = -24 2. tokenizer.ignore(-24) moves the read position backward by 24 bytes 3. extensionSize -= 0 (loop counter never decreases) 4. while (extensionSize 0) never exits 5. The same 24-byte header is re-read infinitely This is the same pattern as CVE-2026-31808 (GHSA-5v7r-6r5c-r473) in file-type — strtok3's AbstractTokenizer.ignore() accepts negative values without validation. Affected Methods - parseFile() — HANGS (FileTokenizer inherits vulnerable ignore()) - parseBuffer() — HANGS (BufferTokenizer inherits vulnerable ignore()) - parseStream() — NOT affected (ReadStreamTokenizer has own ignore() that throws RangeError) Impact A 100-byte crafted .asf file permanently hangs any application using parseFile() or parseBuffer(). music-metadata…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-v6c2-xwv6-8xf7

  2. Revision 1 · created ·

    Published from osv record GHSA-v6c2-xwv6-8xf7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32256

Advisory: music-metadata has an infinite loop vulnerability in ASF parser
IDs: CVE-2026-32256, GHSA-v6c2-xwv6-8xf7
Record: https://patchnext.com/advisories/cve-2026-32256 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: music-metadata 11.12.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm music-metadata: affected <= 11.12.1; fixed in 11.12.3

## Suggested inspection (read-only)
- `npm ls music-metadata --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on music-metadata.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v6c2-xwv6-8xf7 (OSV record GHSA-v6c2-xwv6-8xf7 lists affected ranges: npm music-metadata >=0 <11.12.3 (fixed))
- Verified: https://github.com/advisories/GHSA-v6c2-xwv6-8xf7 (GitHub-reviewed advisory GHSA-v6c2-xwv6-8xf7 lists affected ranges: npm music-metadata >=0 <=11.12.1)

Commands are suggestions: review each one before running it.

Loading voting…