CVE-2026-107392

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-08) is not newer than that change (2026-10-13), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-95248 (ENISA EUVD) · GHSA-8j4c-6x6g-rq3j (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

music-metadata is a metadata parser for audio and video media files. Prior to 11.15.0, the DSF parser handles an unrecognized chunk by calling tokenizer.ignore without awaiting the returned promise and without first rejecting a chunk size smaller than the 12-byte chunk header. A crafted DSF input can produce a negative ignore length; with strtok3 10.3.5 or later, the resulting RangeError is detached from the parseBuffer promise and becomes an unhandled rejection under Node.js default behavior. The parse call can appear to resolve before the process crashes, bypassing per-parse try/catch handling. The demonstrated impact is availability loss only and requires the DSF parsing path. This issue is fixed in version 11.15.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 8, 2026

Last Modified

October 13, 2026

Advisory Details (4)

Auto-updated Oct 8, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

Release v11.15.0 (Borewit/music-metadata)

Patch available: Borewit/music-metadata v11.15.0

https://github.com/Borewit/music-metadata/releases/tag/v11.15.0
GitHub commit Patch Available

commit e7fc27a96e78 (Borewit/music-metadata)

Patch available: Borewit/music-metadata v11.15.0 (contains commit e7fc27a96e78)

https://github.com/Borewit/music-metadata/commit/e7fc27a96e789d41ece41fdac590fc7618274a41
GitHub pull request Patch Available

Fix DSF parsing of malformed chunk sizes.

Patch available: Borewit/music-metadata v11.15.0 (PR #2700 merged 2026-08-18)

https://github.com/Borewit/music-metadata/pull/2700
GitHub advisoryMentions a patch (unverified)

uncatchable process crash parsing a crafted `.dsf` (residual of GHSA-v6c2-xwv6-8xf7) · Advisory · Borewit/music-metadata · GitHub

Affected: 11.12.3 (size validation) and strtok3

https://github.com/Borewit/music-metadata/security/advisories/GHSA-8j4c-6x6g-rq3j

Vendor Advisories for CVE-2026-107392(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmmusic-metadata @ 11.15.0 (fixes <= 11.14.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
music-metadata—
  • every version up to 11.15.0: fixed in 11.15.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-8j4c-6x6g-rq3j · GitHub severity MODERATE · GitHub CVSS 6.2
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-27 23:21 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-25 14:54 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-20 19:12 UTCEG score recompute
  18. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 05:07 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 18 more
  1. 2026-10-13 20:02 UTCEG score recompute▲ 1.30
  2. 2026-10-13 19:44 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-12 16:38 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-11 20:14 UTCEG score recompute
  7. 2026-10-11 18:26 UTCEG score recompute
  8. 2026-10-11 15:00 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-11 01:38 UTCEG score recompute
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-09 23:17 UTCEG score recompute
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-08 20:56 UTCEG score recompute
  15. 2026-10-08 20:19 UTCEG score recompute
  16. 2026-10-08 20:02 UTCEG score recompute
  17. 2026-10-08 19:25 UTCEG score recomputeFirst assessed: 6.2 MEDIUM
  18. 2026-10-08 19:24 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-107392?
CVE-2026-107392 is a high-severity vulnerability; its CVE record was published on October 8, 2026. music-metadata is a metadata parser for audio and video media files. Prior to 11.15.0, the DSF parser handles an unrecognized chunk by calling tokenizer.ignore without awaiting the returned promise and without first rejecting a chunk size smaller than the 12-byte chunk header. A crafted DSF input…
When was the CVE record for CVE-2026-107392 published?
The CVE record for CVE-2026-107392 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-107392 actively exploited?
CVE-2026-107392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107392?
CVE-2026-107392 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-107392?
A fix for CVE-2026-107392 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107392 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107392

Explore →

Is Your Infrastructure Affected by CVE-2026-107392?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs