<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 17:07:52 +0000</lastBuildDate>
    <item>
      <title>BIT-pillow-2026-112396 — Pillow: Heap use-after-free when encoding TIFF to an in-memory buffer</title>
      <link>https://cve.radiocsirt.org/vuln/bit-pillow-2026-112396</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-pillow-2026-112396</guid>
    </item>
    <item>
      <title>BREW-aider-CVE-2026-112396 — Pillow: Heap use-after-free when encoding TIFF to an in-memory buffer</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-112396</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary
Saving an image as TIFF to an in-memory buffer can trigger a heap use-after-free if libtiff rejects a tag at encode time. When `TIFFWriteScanline` fails, the encoder frees its output buffer but leaves the libtiff handle open. Later, when the encoder object is torn down, `TIFFClose` flushes buffered bytes through the write callback and writes into the freed buffer. An application that re-encodes attacker-influenced images to TIFF in memory can be crashed and is a candidate for remote code execution.&lt;/p&gt;
&lt;p&gt;### Details
The failure path in `ImagingLibTiffEncode` frees `clientstate-&amp;gt;data` for the in-memory case but does not close the TIFF or null `clientstate-&amp;gt;tiff` (the file-descriptor branch just above it does set `tiff = NULL`):&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:1041-1046`&lt;/p&gt;
&lt;p&gt;Teardown then calls `ImagingLibTiffEncodeCleanup`, which runs `TIFFClose(tiff)` because `tiff` is still set:&lt;/p&gt;
&lt;p&gt;- `src/encode.c:99-101`
- `src/libImaging/TiffDecode.c:955`&lt;/p&gt;
&lt;p&gt;`TIFFClose` flushes through `_tiffWriteProc`, which reallocs and memcpys into the freed `state-&amp;gt;data`:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:103-115`&lt;/p&gt;
&lt;p&gt;The Predictor tag is a convenient trigger: the floating-point predictor (value 3) is invalid for integer sample data, so libtiff aborts the write.&lt;/p&gt;
&lt;p&gt;### PoC
```python
import io
from PIL import Image&lt;/p&gt;
&lt;p&gt;# In-memory TIFF re-encode. libtiff rejects Predictor=3 (floating point) on integer
# data, so TIFFWriteScanline fails. The encoder frees clientstate-&amp;gt;data but leaves the
# TIFF open; cleanup&amp;#39;s TI…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary
Saving an image as TIFF to an in-memory buffer can trigger a heap use-after-free if libtiff rejects a tag at encode time. When `TIFFWriteScanline` fails, the encoder frees its output buffer but leaves the libtiff handle open. Later, when the encoder object is torn down, `TIFFClose` flushes buffered bytes through the write callback and writes into the freed buffer. An application that re-encodes attacker-influenced images to TIFF in memory can be crashed and is a candidate for remote code execution.&lt;/p&gt;
&lt;p&gt;### Details
The failure path in `ImagingLibTiffEncode` frees `clientstate-&amp;gt;data` for the in-memory case but does not close the TIFF or null `clientstate-&amp;gt;tiff` (the file-descriptor branch just above it does set `tiff = NULL`):&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:1041-1046`&lt;/p&gt;
&lt;p&gt;Teardown then calls `ImagingLibTiffEncodeCleanup`, which runs `TIFFClose(tiff)` because `tiff` is still set:&lt;/p&gt;
&lt;p&gt;- `src/encode.c:99-101`
- `src/libImaging/TiffDecode.c:955`&lt;/p&gt;
&lt;p&gt;`TIFFClose` flushes through `_tiffWriteProc`, which reallocs and memcpys into the freed `state-&amp;gt;data`:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:103-115`&lt;/p&gt;
&lt;p&gt;The Predictor tag is a convenient trigger: the floating-point predictor (value 3) is invalid for integer sample data, so libtiff aborts the write.&lt;/p&gt;
&lt;p&gt;### PoC
```python
import io
from PIL import Image&lt;/p&gt;
&lt;p&gt;# In-memory TIFF re-encode. libtiff rejects Predictor=3 (floating point) on integer
# data, so TIFFWriteScanline fails. The encoder frees clientstate-&amp;gt;data but leaves the
# TIFF open; cleanup&amp;#39;s TI…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-112396</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486</link>
      <description>certfr-2026-avi-1486</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1486</guid>
    </item>
    <item>
      <title>CLEANSTART-2026-DT28278 — Pillow is a Python imaging library</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-dt28278</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: apache-superset&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the apache-superset package. Pillow is a Python imaging library.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: apache-superset&lt;/p&gt;
&lt;p&gt;Security vulnerability affects the apache-superset package. Pillow is a Python imaging library.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-dt28278</guid>
    </item>
    <item>
      <title>EUVD-2026-389713</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-389713</link>
      <description>EUVD-2026-389713</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-389713</guid>
    </item>
    <item>
      <title>fkie_cve-2026-112396</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-112396</link>
      <description>&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-112396</guid>
    </item>
    <item>
      <title>GHSA-4rr5-89j8-mwwm — Pillow: Heap use-after-free when encoding TIFF to an in-memory buffer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4rr5-89j8-mwwm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pillow&lt;/p&gt;
&lt;p&gt;### Summary
Saving an image as TIFF to an in-memory buffer can trigger a heap use-after-free if libtiff rejects a tag at encode time. When `TIFFWriteScanline` fails, the encoder frees its output buffer but leaves the libtiff handle open. Later, when the encoder object is torn down, `TIFFClose` flushes buffered bytes through the write callback and writes into the freed buffer. An application that re-encodes attacker-influenced images to TIFF in memory can be crashed and is a candidate for remote code execution.&lt;/p&gt;
&lt;p&gt;### Details
The failure path in `ImagingLibTiffEncode` frees `clientstate-&amp;gt;data` for the in-memory case but does not close the TIFF or null `clientstate-&amp;gt;tiff` (the file-descriptor branch just above it does set `tiff = NULL`):&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:1041-1046`&lt;/p&gt;
&lt;p&gt;Teardown then calls `ImagingLibTiffEncodeCleanup`, which runs `TIFFClose(tiff)` because `tiff` is still set:&lt;/p&gt;
&lt;p&gt;- `src/encode.c:99-101`
- `src/libImaging/TiffDecode.c:955`&lt;/p&gt;
&lt;p&gt;`TIFFClose` flushes through `_tiffWriteProc`, which reallocs and memcpys into the freed `state-&amp;gt;data`:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:103-115`&lt;/p&gt;
&lt;p&gt;The Predictor tag is a convenient trigger: the floating-point predictor (value 3) is invalid for integer sample data, so libtiff aborts the write.&lt;/p&gt;
&lt;p&gt;### PoC
```python
import io
from PIL import Image&lt;/p&gt;
&lt;p&gt;# In-memory TIFF re-encode. libtiff rejects Predictor=3 (floating point) on integer
# data, so TIFFWriteScanline fails. The encoder frees clientstate-&amp;gt;data but leaves the
# TIFF open; cleanup&amp;#39;s TI…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pillow&lt;/p&gt;
&lt;p&gt;### Summary
Saving an image as TIFF to an in-memory buffer can trigger a heap use-after-free if libtiff rejects a tag at encode time. When `TIFFWriteScanline` fails, the encoder frees its output buffer but leaves the libtiff handle open. Later, when the encoder object is torn down, `TIFFClose` flushes buffered bytes through the write callback and writes into the freed buffer. An application that re-encodes attacker-influenced images to TIFF in memory can be crashed and is a candidate for remote code execution.&lt;/p&gt;
&lt;p&gt;### Details
The failure path in `ImagingLibTiffEncode` frees `clientstate-&amp;gt;data` for the in-memory case but does not close the TIFF or null `clientstate-&amp;gt;tiff` (the file-descriptor branch just above it does set `tiff = NULL`):&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:1041-1046`&lt;/p&gt;
&lt;p&gt;Teardown then calls `ImagingLibTiffEncodeCleanup`, which runs `TIFFClose(tiff)` because `tiff` is still set:&lt;/p&gt;
&lt;p&gt;- `src/encode.c:99-101`
- `src/libImaging/TiffDecode.c:955`&lt;/p&gt;
&lt;p&gt;`TIFFClose` flushes through `_tiffWriteProc`, which reallocs and memcpys into the freed `state-&amp;gt;data`:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/TiffDecode.c:103-115`&lt;/p&gt;
&lt;p&gt;The Predictor tag is a convenient trigger: the floating-point predictor (value 3) is invalid for integer sample data, so libtiff aborts the write.&lt;/p&gt;
&lt;p&gt;### PoC
```python
import io
from PIL import Image&lt;/p&gt;
&lt;p&gt;# In-memory TIFF re-encode. libtiff rejects Predictor=3 (floating point) on integer
# data, so TIFFWriteScanline fails. The encoder frees clientstate-&amp;gt;data but leaves the
# TIFF open; cleanup&amp;#39;s TI…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4rr5-89j8-mwwm</guid>
    </item>
    <item>
      <title>PYSEC-2026-4328</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-4328</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-4328</guid>
    </item>
    <item>
      <title>RHSA-2026:94702 — Red Hat Security Advisory: Red Hat AI Inference 3.5.3 (CPU)</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:94702</link>
      <description>&lt;p&gt;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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:94702</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-112396</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-112396</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: pillow-python2, Ubuntu:26.10: pillow, Ubuntu:26.04:LTS: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: pillow-python2, Ubuntu:26.10: pillow, Ubuntu:26.04:LTS: pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 11.3.0 until 13.0.0, Pillow has a heap use-after-free when libtiff rejects a tag while encoding TIFF data to an in-memory buffer. When an application saves attacker-influenced TIFF tags to BytesIO, libtiff can reject a tag during encoding in ImagingLibTiffEncode; the error path then frees the output buffer without closing or clearing the TIFF handle, and later cleanup flushes through the write callback into freed memory, which can crash the process and may enable code execution. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-112396</guid>
    </item>
  </channel>
</rss>
