CVE-2026-107392 json
music-metadata: uncatchable process crash parsing a crafted `.dsf` (residual of CVE-2026-32256)
published last mo. modified 27d ago also EUVD-2026-95248 , GHSA-8j4c-6x6g-rq3j
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm music-metadata 11.15.0
- borewit music-metadata 11.15.0
Is CVE-2026-107392 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/Borewit/music-metadata/security/advisories/GHSA-8j4c-6x6g-rq3j referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | music-metadata | <11.15.0 |
11.15.0 |
Affected products
- Borewit music-metadata
Classification
References
-
github.com
/Borewit/music-metadata/pull/2700
web, patch
-
github.com
/Borewit/music-metadata/commit/e7fc27a96e789d41ece41fdac590fc7618274a41
web, patch
-
github.com
/Borewit/music-metadata/releases/tag/v11.15.0
web, patch, release-notes, vendor-advisory
-
github.com
/Borewit/music-metadata/security/advisories/GHSA-8j4c-6x6g-rq3j
exploit, web, vendor-advisory
-
github.com
/Borewit/music-metadata
package
Sources
- CVE List CVE-2026-107392
- GitHub Advisory GHSA-8j4c-6x6g-rq3j
- NVD CVE-2026-107392
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.