<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-10T19:00:01.813409+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-107387</id>
    <title>fkie_cve-2026-107387</title>
    <updated>2026-10-10T19:00:02.130932+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-107387"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-53v6-4h7p-p4gj</id>
    <title>GHSA-53v6-4h7p-p4gj — music-metadata: Uncontrolled memory allocation in APEv2 parser</title>
    <updated>2026-10-10T19:00:02.131058+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: music-metadata</p>
<p>## Summary</p>
<p>`music-metadata` 11.15.0 is vulnerable to uncontrolled memory allocation in the APEv2 parser.</p>
<p>The parser reads the size of an APEv2 tag item from the input file and uses that value to allocate memory before checking whether the file actually contains that many bytes. A small crafted `.ape` file can declare a very large binary tag item, such as cover art, and force the parser to allocate a large buffer.</p>
<p>This issue is specific to APEv2 parsing and is separate from the ID3v2, MP4, and EBML advisories.</p>
<p>## Affected component</p>
<p>- `lib/apev2/APEv2Token.ts`
- `lib/apev2/APEv2Parser.ts`</p>
<p>The untrusted size is read here:</p>
<p>```ts
size: Token.UINT32_LE.get(buf, off)
```</p>
<p>It is later used directly for allocation when parsing binary tag items:</p>
<p>```ts
const picData = new Uint8Array(tagItemHeader.size);
await this.tokenizer.readBuffer(picData);
```</p>
<p>The allocation happens before the parser confirms that the declared size fits inside the remaining file data.</p>
<p>## Impact</p>
<p>An application that parses untrusted `.ape` files with `music-metadata` may be vulnerable to denial of service through memory exhaustion.</p>
<p>The demonstrated payload is only 134 bytes but causes a 128 MiB allocation with default options. Concurrent or repeated parses can multiply the memory impact.</p>
<p>The impact is limited to availability. No confidentiality or integrity impact has been demonstrated.</p>
<p>## Proof of Concept</p>
<p>Run from the project checkout after compiling the source:</p>
<p>```bash
npm install --ignore-scripts…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-53v6-4h7p-p4gj"/>
  </entry>
</feed>
