Skip to content

← Actionable
Medium, CVSS 6.2amended

music-metadata: EBML parser trusts element lengths, allowing memory exhaustion or process abort

CVE-2026-107389GHSA-5gfj-9q3v-qfp3

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

Sources

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-107389: 0.21% estimated exploitation activity in the next 30 days; percentile 11.82 (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 The Matroska/WebM EBML parser decodes attacker-controlled variable-length integer (VINT) element lengths without first validating that the declared element fits within its enclosing container or the available input. Leaf lengths are then used directly for string-token and Uint8Array allocations. A very small crafted .webm, .mkv, or .mka file can therefore cause a disproportionately large allocation, an out-of-memory denial of service, or—in one demonstrated parseFile case—an uncatchable V8 fatal abort. Impact Applications that parse untrusted Matroska/WebM media can be denied service. Depending on the input, parser API, and Node.js/V8 version, the demonstrated outcomes include: - a 34-byte input causing an approximately 128 MiB allocation before end-of-input; - a 70-byte input causing a 500 MiB allocation through a binary EBML leaf, with concurrent parses multiplying memory consumption; - a 48-byte file causing an uncatchable V8 fatal abort through parseFile when a leaf…

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

    Amended from ghsa record GHSA-5gfj-9q3v-qfp3

  2. Revision 2 · amended ·

    Amended from osv record GHSA-5gfj-9q3v-qfp3

  3. Revision 1 · created ·

    Published from ghsa record GHSA-5gfj-9q3v-qfp3

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-107389

Advisory: music-metadata: EBML parser trusts element lengths, allowing memory exhaustion or process abort
IDs: CVE-2026-107389, GHSA-5gfj-9q3v-qfp3
Record: https://patchnext.com/advisories/cve-2026-107389 (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-5gfj-9q3v-qfp3 (GitHub-reviewed advisory GHSA-5gfj-9q3v-qfp3 lists affected ranges: npm music-metadata >=0 <11.16.0)
- Verified: https://osv.dev/vulnerability/GHSA-5gfj-9q3v-qfp3 (OSV record GHSA-5gfj-9q3v-qfp3 lists affected ranges: npm music-metadata >=0 <11.16.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…