music-metadata: MP4 stsd sample-entry size==0 causes a synchronous infinite loop (DoS) — unreleased regression on master
CVE-2026-107391GHSA-f94x-6692-553q
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (music-metadata 11.16.0), 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.
Affected packages
npm music-metadata
- Affected
- < 11.16.0
- Fixed in
- 11.16.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f94x-6692-553q lists affected ranges: npm music-metadata >=0 <11.16.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f94x-6692-553q lists affected ranges: npm music-metadata >=0 <11.16.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- CVE-2026-107391: 0.32% estimated exploitation activity in the next 30 days; percentile 24.61 (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 StsdAtom.get() in lib/mp4/AtomToken.ts parses an MP4 stsd (sample description) box's entry table by advancing a cursor with off += size - 4, where size is a 32-bit, attacker-controlled per-entry length read straight from the file. When size == 0, that advance is 0, so a file declaring a huge entrycount and a first entry size of 0 spins forever: same bytes read every iteration, no progress, no exit. Because StsdAtom.get runs synchronously inside strtok3's tokenizer, this doesn't just fail slowly — it blocks the Node.js event loop entirely for the whole process. A 48-byte file is enough to hang any service that parses user-uploaded audio/video metadata through parseBuffer, parseFile, parseStream, parseBlob, or parseWebStream. This is currently unreleased — present on the master branch only, not in the latest npm release (11.14.0) or any earlier one. Reporting now, before it ships. Details lib/mp4/AtomToken.ts, StsdAtom.get(): - Introduced by commit d2a7d6f ("fix(mp4): locate…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-f94x-6692-553q
- Revision 2 · amended ·
Amended from osv record GHSA-f94x-6692-553q
- Revision 1 · created ·
Published from ghsa record GHSA-f94x-6692-553q
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-107391 Advisory: music-metadata: MP4 stsd sample-entry size==0 causes a synchronous infinite loop (DoS) — unreleased regression on master IDs: CVE-2026-107391, GHSA-f94x-6692-553q Record: https://patchnext.com/advisories/cve-2026-107391 (revision 3, source checked 26 Oct 2026, 13:07 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.2) 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.16.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm music-metadata: affected < 11.16.0; fixed in 11.16.0 ## 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://github.com/advisories/GHSA-f94x-6692-553q (GitHub-reviewed advisory GHSA-f94x-6692-553q lists affected ranges: npm music-metadata >=0 <11.16.0) - Verified: https://osv.dev/vulnerability/GHSA-f94x-6692-553q (OSV record GHSA-f94x-6692-553q lists affected ranges: npm music-metadata >=0 <11.16.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…