CVE-2026-107387

music-metadata: Uncontrolled memory allocation in APEv2 parser

Published Oct 8, 2026 CVSS 3.1 · 6.2 Medium EPSS < 1% KEV · Not listed
Description
music-metadata is a metadata parser for audio and video media files. Prior to 11.16.0, the APEv2 parser reads an attacker-controlled tag-item size and allocates a Uint8Array for a binary item before proving that the declared item fits in the remaining tag or file data. A small crafted APE file can therefore trigger a disproportionate allocation, including through cover-art items, and repeated or concurrent parsing can exhaust process memory. The demonstrated impact is availability loss only. This issue is fixed in version 11.16.0.

Analysis

AI-generated

Technical impact

In music-metadata’s APEv2 parser, an attacker‑controlled tag‑item size is read before confirming that the item fits within the remaining tag or file data. This oversight allows a disproportionately large Uint8Array to be allocated, leading to memory exhaustion and application crashes. The vulnerability manifests only as availability loss and is classified as CWE‑789, uncontrolled memory allocation.

Affected Systems

Any use of Borewit’s music-metadata library prior to version 11.16.0 is affected. The fix applied in v11.16.0 verifies tag sizes before allocation, eliminating the dangerous memory growth. Systems that parse user‑supplied or third‑party media files with this library—such as Node.js applications or media players—must review their dependency versions.

Risk and Exploitability

The CVSS score of 6.2 indicates moderate severity. EPSS data is not available, and the issue is not listed in CISA KEV. An attacker can exploit the flaw simply by providing a crafted APE file containing oversized tag items; no additional privileges or code execution are required. Successful exploitation leads to total application interruption through memory exhaustion, but it does not impact confidentiality or integrity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade music‑metadata to version 11.16.0 or later to apply the tag‑size validation fix.
  • Verify that only trusted media files are parsed; reject or sanitize untrusted files before invoking the library.
  • Run the parsing routine in a sandboxed or memory‑restricted environment and monitor for abnormal memory consumption.
  • If immediate upgrade is not possible, disable APE tag processing or strip cover‑art extraction from the application logic.

Generated by OpenCVE AI on October 8, 2026 at 20:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-53v6-4h7p-p4gj music-metadata: Uncontrolled memory allocation in APEv2 parser
History
Type Values Removed Values Added
CPEs cpe:2.3:a:borewit:music-metadata:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Borewit
Borewit music-metadata
Vendors & Products Borewit
Borewit music-metadata
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description music-metadata is a metadata parser for audio and video media files. Prior to 11.16.0, the APEv2 parser reads an attacker-controlled tag-item size and allocates a Uint8Array for a binary item before proving that the declared item fits in the remaining tag or file data. A small crafted APE file can therefore trigger a disproportionate allocation, including through cover-art items, and repeated or concurrent parsing can exhaust process memory. The demonstrated impact is availability loss only. This issue is fixed in version 11.16.0.
Title music-metadata: Uncontrolled memory allocation in APEv2 parser
Weaknesses CWE-789
References
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 8, 2026, 7:32 PM
Reserved
Oct 7, 2026, 9:07 PM
Status
Analyzed
Published
Oct 8, 2026, 7:17 PM
Modified
Oct 13, 2026, 2:35 PM