<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T18:26:57.960498+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bit-pillow-2026-96642</id>
    <title>BIT-pillow-2026-96642 — Pillow: TarIO negative size field causes infinite CPU-spin loop</title>
    <updated>2026-11-16T18:26:58.004452+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: pillow</p>
<p>Pillow is a Python imaging library. Prior to 13.0.0, the TarIO initializer in src/PIL/TarIO.py accepts a negative octal member size and computes a backward seek that returns to the same 512-byte header. When the requested member name does not match, the parser repeatedly reads that header, consumes a full CPU core, and never returns. TarIO is reached only when an application directly uses PIL.TarIO.TarIO rather than the default Image.open() path. This issue is fixed in version 13.0.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-pillow-2026-96642"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-96642</id>
    <title>BREW-aider-CVE-2026-96642 — Pillow: TarIO negative size field causes infinite CPU-spin loop</title>
    <updated>2026-11-16T18:26:58.004539+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: aider</p>
<p>### Summary
`TarIO.__init__` does not check that a tar header's size field is positive. A crafted header with a negative size makes it seek backward onto itself. This causes an infinite loop that uses 100% CPU and never returns.</p>
<p>### Details
`TarIO.__init__` reads 512-byte tar headers one at a time, looking for a member with a given name. For each header it reads the size field and skips ahead to the next header:</p>
<p>```python
size = int(s[124:135], 8)
...
self.fh.seek((size + 511) &amp; (~511), io.SEEK_CUR)
```
There is no check that size is zero or more. A tar header can set this field to a negative octal value. For size = -512, the seek offset comes out to exactly -512, which cancels the 512 bytes the loop had just read. The file position goes right back to where this loop step started.</p>
<p>The loop only stops on end of file or when a header name starts with a null byte. Neither happens, since the same header keeps showing up again. The loop never ends on its own.</p>
<p>### Steps to reproduce</p>
<p>This uses Tests/images/hopper.tar, a normal file already in the Pillow test suite. It only changes the size field of the first header.</p>
<p>```python
from PIL import TarIO</p>
<p>with open("Tests/images/hopper.tar", "rb") as f:
    data = bytearray(f.read())</p>
<p># Set the size field (bytes 124 to 135) to a negative octal value.
# Octal 1000 is 512, so this is size = -512.
data[124:135] = b"  -00001000"</p>
<p>with open("poisoned.tar", "wb") as f:
    f.write(data)</p>
<p># "does-not-exist" does not match the header name,…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-96642"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486</id>
    <title>certfr-2026-avi-1486 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-11-16T18:26:58.004606+00:00</updated>
    <content>certfr-2026-avi-1486</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-hb81813</id>
    <title>CLEANSTART-2026-HB81813 — Pillow is a Python imaging library</title>
    <updated>2026-11-16T18:26:58.004626+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: apache-superset</p>
<p>Security vulnerability affects the apache-superset package. Pillow is a Python imaging library.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-hb81813"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396525</id>
    <title>EUVD-2026-396525</title>
    <updated>2026-11-16T18:26:58.004646+00:00</updated>
    <content>EUVD-2026-396525</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396525"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-96642</id>
    <title>fkie_cve-2026-96642</title>
    <updated>2026-11-16T18:26:58.004658+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Pillow is a Python imaging library. Prior to 13.0.0, the TarIO initializer in src/PIL/TarIO.py accepts a negative octal member size and computes a backward seek that returns to the same 512-byte header. When the requested member name does not match, the parser repeatedly reads that header, consumes a full CPU core, and never returns. TarIO is reached only when an application directly uses PIL.TarIO.TarIO rather than the default Image.open() path. This issue is fixed in version 13.0.0.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-96642"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3j72-p6qg-6xp7</id>
    <title>GHSA-3j72-p6qg-6xp7 — Pillow: TarIO negative size field causes infinite CPU-spin loop</title>
    <updated>2026-11-16T18:26:58.004680+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: Pillow</p>
<p>### Summary
`TarIO.__init__` does not check that a tar header's size field is positive. A crafted header with a negative size makes it seek backward onto itself. This causes an infinite loop that uses 100% CPU and never returns.</p>
<p>### Details
`TarIO.__init__` reads 512-byte tar headers one at a time, looking for a member with a given name. For each header it reads the size field and skips ahead to the next header:</p>
<p>```python
size = int(s[124:135], 8)
...
self.fh.seek((size + 511) &amp; (~511), io.SEEK_CUR)
```
There is no check that size is zero or more. A tar header can set this field to a negative octal value. For size = -512, the seek offset comes out to exactly -512, which cancels the 512 bytes the loop had just read. The file position goes right back to where this loop step started.</p>
<p>The loop only stops on end of file or when a header name starts with a null byte. Neither happens, since the same header keeps showing up again. The loop never ends on its own.</p>
<p>### Steps to reproduce</p>
<p>This uses Tests/images/hopper.tar, a normal file already in the Pillow test suite. It only changes the size field of the first header.</p>
<p>```python
from PIL import TarIO</p>
<p>with open("Tests/images/hopper.tar", "rb") as f:
    data = bytearray(f.read())</p>
<p># Set the size field (bytes 124 to 135) to a negative octal value.
# Octal 1000 is 512, so this is size = -512.
data[124:135] = b"  -00001000"</p>
<p>with open("poisoned.tar", "wb") as f:
    f.write(data)</p>
<p># "does-not-exist" does not match the header name,…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3j72-p6qg-6xp7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-4341</id>
    <title>PYSEC-2026-4341</title>
    <updated>2026-11-16T18:26:58.004724+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pillow</p>
<p>Pillow is a Python imaging library. Prior to 13.0.0, the TarIO initializer in src/PIL/TarIO.py accepts a negative octal member size and computes a backward seek that returns to the same 512-byte header. When the requested member name does not match, the parser repeatedly reads that header, consumes a full CPU core, and never returns. TarIO is reached only when an application directly uses PIL.TarIO.TarIO rather than the default Image.open() path. This issue is fixed in version 13.0.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-4341"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:94702</id>
    <title>RHSA-2026:94702 — Red Hat Security Advisory: Red Hat AI Inference 3.5.3 (CPU)</title>
    <updated>2026-11-16T18:26:58.004744+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>mcp: mcp: Denial of Service via session memory exhaustion in streamable HTTP servers vllm: vLLM: Denial of Service via Regular Expression processing vllm: vLLM: Denial of Service via negative token ID input vllm: vLLM: Denial of Service via unbounded P2P KV offloading sessions pillow: pillow: Denial of Service via decompression bomb check bypass in multi-frame images pillow: pillow: Denial of Service via decompression bomb bypass in SPIDER images pillow: pillow: Denial of Service via crafted RLE BMP image pillow: Pillow multi-frame loaders can reuse stale native image storage after mode transitions pillow: pillow: Denial of Service via duplicate page references in PDF files pillow: pillow: Denial of Service via integer overflow in text-width calculation pillow: Pillow: Denial of Service via negative archive member size in TarIO pillow: pillow: Denial of Service via repeated EXIF headers pillow: Pillow: Denial of Service via out-of-bounds read in metafile parser pillow: pillow: Arbitrary code execution via JPEG encoder buffer overflow vllm: vLLM: Denial of Service via unbounded media ingestion aiohttp: aiohttp: Information disclosure via unenforced Secure attribute on shared cookies aiohttp: aiohttp: Denial of Service via missing initial request timeout aiohttp: aiohttp: Denial of Service via Max-Age processing overflow aiohttp: aiohttp: Denial of Service via file descriptor exhaustion in multipart request processing aiohttp: aiohttp: Security control bypass via request schem…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:94702"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-96642</id>
    <title>UBUNTU-CVE-2026-96642</title>
    <updated>2026-11-16T18:26:58.004862+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: pillow, Ubuntu:Pro:16.04:LTS: pillow, Ubuntu:Pro:18.04:LTS: pillow, Ubuntu:Pro:20.04:LTS: pillow, Ubuntu:Pro:20.04:LTS: pillow-python2, Ubuntu:22.04:LTS: pillow, Ubuntu:24.04:LTS: pillow, Ubuntu:26.10: pillow, Ubuntu:26.04:LTS: pillow</p>
<p>Pillow is a Python imaging library. Prior to 13.0.0, the TarIO initializer in src/PIL/TarIO.py accepts a negative octal member size and computes a backward seek that returns to the same 512-byte header. When the requested member name does not match, the parser repeatedly reads that header, consumes a full CPU core, and never returns. TarIO is reached only when an application directly uses PIL.TarIO.TarIO rather than the default Image.open() path. This issue is fixed in version 13.0.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-96642"/>
  </entry>
</feed>
