# CVE-2026-32256: music-metadata has an infinite loop vulnerability in ASF parser

> An attacker can cause a denial of service by providing a crafted ASF file that triggers an infinite loop in the music-metadata parser.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-v6c2-xwv6-8xf7, MINI-4pmg-2rrh-997j

## What is CVE-2026-32256?

CVE-2026-32256 is a high-severity denial of service vulnerability in Borewit music-metadata, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-32256?

2 open source packages ship an affected version, including music-metadata. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `music-metadata` | npm | All versions | 11.12.3 |
| `music-metadata` | npm | All versions | 11.12.3 |

Products: Borewit Music-Metadata.

## How do I fix CVE-2026-32256?

Upgrade music-metadata to 11.12.3 or later.

## Is CVE-2026-32256 being exploited?

There is no known exploitation of CVE-2026-32256 in the wild and no public exploit code.

## Other vulnerabilities in Borewit music-metadata

- [CVE-2026-107387](https://insights.sbomify.com/CVE-2026-107387/): music-metadata: Uncontrolled memory allocation in APEv2 parser (medium 6.2)
- [CVE-2026-107388](https://insights.sbomify.com/CVE-2026-107388/): music-metadata: ID3v2 tag size not validated before allocation, causing memory exhaustion DoS (medium 6.2)
- [CVE-2026-107389](https://insights.sbomify.com/CVE-2026-107389/): music-metadata: EBML parser trusts element lengths, allowing memory exhaustion or process abort (medium 6.2)
- [CVE-2026-107390](https://insights.sbomify.com/CVE-2026-107390/): music-metadata: MP4 parser allows memory exhaustion via oversized extended atom length (medium 6.2)
- [CVE-2026-107391](https://insights.sbomify.com/CVE-2026-107391/): music-metadata: MP4 stsd sample-entry size==0 causes a synchronous infinite loop (DoS) — unreleased regression on master (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32256 and fix it if it is affected.

What it is: CVE-2026-32256 is a high-severity denial of service vulnerability in Borewit music-metadata, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32256 in the wild and no public exploit code.

Affected packages and fixed versions:
- music-metadata (npm): affected all versions; fixed in 11.12.3
- music-metadata (npm): affected all versions; fixed in 11.12.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32256/ (Markdown: https://insights.sbomify.com/CVE-2026-32256/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32256
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32256
- OSV: https://osv.dev/vulnerability/CVE-2026-32256

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32256/
Summaries are generated and may contain mistakes; the official description above is the record.