<?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://db.gcve.eu</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>Thu, 29 Oct 2026 11:04:46 +0000</lastBuildDate>
    <item>
      <title>BREW-aider-CVE-2026-112405 — Pillow: NULL pointer dereference in Image.merge via an unvalidated band 0</title>
      <link>https://db.gcve.eu/vuln/brew-aider-cve-2026-112405</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary
`Image.merge()` checks the mode of every input band except band 0. If band 0 is a single-band `I` or `F` image, the native merge routine reads a pixel pointer that is NULL for those modes and the process crashes. The IPTC plugin reaches this from a plain `Image.open()` followed by a load, and IPTC has no magic-byte prefilter, so a crafted file with no recognizable header can drive it.&lt;/p&gt;
&lt;p&gt;### Details
The validation loop skips band 0:&lt;/p&gt;
&lt;p&gt;- `src/PIL/Image.py:3795` iterates `for band in bands[1:]` and checks mode and size only for those.&lt;/p&gt;
&lt;p&gt;For an `I` or `F` image the 8-bit plane `image8` is NULL (only `image32` is set). `ImagingMerge` dereferences `bands[0]-&amp;gt;image8[y]` for the multi-band output modes:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/Bands.c:302`, `:311`, `:321`&lt;/p&gt;
&lt;p&gt;The IPTC loader builds the band list from an attacker-typed sub-image and passes it to merge with the sub-image at index 0:&lt;/p&gt;
&lt;p&gt;- `src/PIL/IptcImagePlugin.py:156-160`
- `src/PIL/IptcImagePlugin.py:169` registers the opener with no accept function.&lt;/p&gt;
&lt;p&gt;### PoC
```python
from PIL import Image&lt;/p&gt;
&lt;p&gt;# Band 0 is a single-band &amp;#34;I&amp;#34; image: its image8 plane is NULL. merge() validates only
# bands[1:], so the native ImagingMerge dereferences the NULL plane for band 0.
band0 = Image.new(&amp;#34;I&amp;#34;, (4, 4))
Image.merge(&amp;#34;RGB&amp;#34;, [band0, Image.new(&amp;#34;L&amp;#34;, (4, 4)), Image.new(&amp;#34;L&amp;#34;, (4, 4))])
```&lt;/p&gt;
&lt;p&gt;Run it:
```
$ python 02_poc.py
Segmentation fault (core dumped)
```&lt;/p&gt;
&lt;p&gt;Observed on a source build of commit `3e2ab96`.&lt;/p&gt;
&lt;p&gt;Under AddressSanitizer:
```
==ERROR: AddressSanitizer…&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
`Image.merge()` checks the mode of every input band except band 0. If band 0 is a single-band `I` or `F` image, the native merge routine reads a pixel pointer that is NULL for those modes and the process crashes. The IPTC plugin reaches this from a plain `Image.open()` followed by a load, and IPTC has no magic-byte prefilter, so a crafted file with no recognizable header can drive it.&lt;/p&gt;
&lt;p&gt;### Details
The validation loop skips band 0:&lt;/p&gt;
&lt;p&gt;- `src/PIL/Image.py:3795` iterates `for band in bands[1:]` and checks mode and size only for those.&lt;/p&gt;
&lt;p&gt;For an `I` or `F` image the 8-bit plane `image8` is NULL (only `image32` is set). `ImagingMerge` dereferences `bands[0]-&amp;gt;image8[y]` for the multi-band output modes:&lt;/p&gt;
&lt;p&gt;- `src/libImaging/Bands.c:302`, `:311`, `:321`&lt;/p&gt;
&lt;p&gt;The IPTC loader builds the band list from an attacker-typed sub-image and passes it to merge with the sub-image at index 0:&lt;/p&gt;
&lt;p&gt;- `src/PIL/IptcImagePlugin.py:156-160`
- `src/PIL/IptcImagePlugin.py:169` registers the opener with no accept function.&lt;/p&gt;
&lt;p&gt;### PoC
```python
from PIL import Image&lt;/p&gt;
&lt;p&gt;# Band 0 is a single-band &amp;#34;I&amp;#34; image: its image8 plane is NULL. merge() validates only
# bands[1:], so the native ImagingMerge dereferences the NULL plane for band 0.
band0 = Image.new(&amp;#34;I&amp;#34;, (4, 4))
Image.merge(&amp;#34;RGB&amp;#34;, [band0, Image.new(&amp;#34;L&amp;#34;, (4, 4)), Image.new(&amp;#34;L&amp;#34;, (4, 4))])
```&lt;/p&gt;
&lt;p&gt;Run it:
```
$ python 02_poc.py
Segmentation fault (core dumped)
```&lt;/p&gt;
&lt;p&gt;Observed on a source build of commit `3e2ab96`.&lt;/p&gt;
&lt;p&gt;Under AddressSanitizer:
```
==ERROR: AddressSanitizer…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/brew-aider-cve-2026-112405</guid>
    </item>
    <item>
      <title>CVE-2026-112405 — Pillow: NULL pointer dereference in Image.merge via an unvalidated band 0</title>
      <link>https://db.gcve.eu/vuln/cve-2026-112405</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-pillow Pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 12.0.0 until 13.0.0, Pillow&amp;#39;s Image.merge() can dereference a null image8 plane. Validation skips the first input band, allowing a 32-bit integer or floating-point image backed by image32 storage to be merged as a narrower multiband image. A crafted IPTC file can reach this path when an application opens and loads it, or a caller can invoke Image.merge() directly with such a first band. This causes a native process crash. 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; python-pillow Pillow&lt;/p&gt;
&lt;p&gt;Pillow is a Python imaging library. From 12.0.0 until 13.0.0, Pillow&amp;#39;s Image.merge() can dereference a null image8 plane. Validation skips the first input band, allowing a 32-bit integer or floating-point image backed by image32 storage to be merged as a narrower multiband image. A crafted IPTC file can reach this path when an application opens and loads it, or a caller can invoke Image.merge() directly with such a first band. This causes a native process crash. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-112405</guid>
    </item>
    <item>
      <title>PYSEC-2026-4333</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-4333</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 12.0.0 until 13.0.0, Pillow&amp;#39;s Image.merge() can dereference a null image8 plane. Validation skips the first input band, allowing a 32-bit integer or floating-point image backed by image32 storage to be merged as a narrower multiband image. A crafted IPTC file can reach this path when an application opens and loads it, or a caller can invoke Image.merge() directly with such a first band. This causes a native process crash. 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 12.0.0 until 13.0.0, Pillow&amp;#39;s Image.merge() can dereference a null image8 plane. Validation skips the first input band, allowing a 32-bit integer or floating-point image backed by image32 storage to be merged as a narrower multiband image. A crafted IPTC file can reach this path when an application opens and loads it, or a caller can invoke Image.merge() directly with such a first band. This causes a native process crash. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-4333</guid>
    </item>
  </channel>
</rss>
