Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-107392 Overview
CVE-2026-107392 affects music-metadata, a popular Node.js metadata parser for audio and video media files maintained by Borewit. Versions prior to 11.15.0 contain an uncaught exception flaw [CWE-248] in the DSD Stream File (DSF) parser. The parser calls tokenizer.ignore on unrecognized chunks without awaiting the returned promise and without validating that the chunk size exceeds the 12-byte chunk header. A crafted DSF file can produce a negative ignore length that triggers a RangeError, which detaches from the parseBuffer promise and surfaces as an unhandled rejection under Node.js default behavior.
Critical Impact
A malicious DSF file processed by any application using music-metadata can crash the Node.js host process, bypassing per-parse try/catch error handling and causing availability loss.
Affected Products
- Borewit music-metadata versions prior to 11.15.0
- Node.js applications that parse user-supplied DSF audio files
- Downstream services that embed music-metadata with strtok3 10.3.5 or later
Discovery Timeline
- 2026-10-08 - CVE-2026-107392 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-107392
Vulnerability Analysis
The flaw resides in the DSF chunk handling logic within lib/dsf/DsfChunk.ts. When the parser encounters an unrecognized chunk, it invokes tokenizer.ignore(chunkSize - headerSize) to skip past the chunk body. Two defects compound in this path. First, the parser does not verify that the declared chunk size is at least the 12-byte header length, allowing arithmetic to produce a negative value. Second, the returned promise is not awaited, so any rejection escapes the enclosing parseBuffer promise chain.
When combined with strtok3 10.3.5 or later, the negative length triggers a synchronous RangeError inside the detached promise. Node.js default behavior treats the unhandled rejection as fatal, terminating the process. The parent parse call can appear to resolve successfully before the crash, defeating any try/catch guard the caller placed around parsing.
Root Cause
The underlying bug is a signed integer interpretation of chunk size fields and a missing await. The patch converts the fields from INT64_LE to UINT64_LE, eliminating the negative-length condition at the type level.
Attack Vector
An attacker supplies a crafted DSF file to any service that routes uploads through music-metadata. This includes media servers, transcoders, tag editors, and cloud ingestion pipelines. No authentication or user interaction is required when the parsing endpoint is network-reachable.
// Patch from lib/dsf/DsfChunk.ts
get: (buf: Uint8Array, off: number): IDsdChunk => {
return {
- fileSize: Token.INT64_LE.get(buf, off),
- metadataPointer: Token.INT64_LE.get(buf, off + 8)
+ fileSize: Token.UINT64_LE.get(buf, off),
+ metadataPointer: Token.UINT64_LE.get(buf, off + 8)
};
};
Source: Borewit music-metadata commit e7fc27a
Detection Methods for CVE-2026-107392
Indicators of Compromise
- Node.js process termination with UnhandledPromiseRejection referencing RangeError and strtok3
- Repeated worker or container restarts shortly after DSF file ingestion
- Upload activity containing .dsf files from untrusted sources with malformed chunk size headers
Detection Strategies
- Inventory application dependencies and flag any music-metadata version below 11.15.0 using software composition analysis
- Enable Node.js --unhandled-rejections=warn in staging to surface the specific stack trace during fuzz testing of DSF inputs
- Correlate media parsing errors in application logs with abrupt process exits in container orchestration telemetry
Monitoring Recommendations
- Alert on process exit codes from Node.js workers that handle user-supplied audio files
- Track parse failure rates and crash loops in media ingestion microservices
- Monitor runtime file-type statistics to identify unusual spikes in DSF uploads
How to Mitigate CVE-2026-107392
Immediate Actions Required
- Upgrade music-metadata to version 11.15.0 or later across all services and build artifacts
- Audit downstream packages that bundle music-metadata as a transitive dependency and refresh lockfiles
- Restrict or disable DSF parsing in untrusted upload pipelines until the upgrade is deployed
Patch Information
The fix is published in music-metadata v11.15.0 and documented in GHSA-8j4c-6x6g-rq3j. The patch is tracked in pull request #2700 and corrects both the signed integer interpretation and the unawaited tokenizer.ignore call.
Workarounds
- Reject DSF files at the application layer by filtering on magic bytes or MIME type until patched
- Wrap parsing in a dedicated worker process so unhandled rejections do not terminate the main service
- Register a process.on('unhandledRejection') handler that logs and recovers instead of crashing, as a defense-in-depth measure
# Upgrade using npm
npm install music-metadata@^11.15.0
# Verify installed version
npm ls music-metadata
# Yarn equivalent
yarn upgrade music-metadata@^11.15.0
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

