<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-29T08:38:10.826889+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-112405</id>
    <title>CVE-2026-112405 — Pillow: NULL pointer dereference in Image.merge via an unvalidated band 0</title>
    <updated>2026-10-29T08:38:10.828266+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> python-pillow Pillow</p>
<p>Pillow is a Python imaging library. From 12.0.0 until 13.0.0, Pillow'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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-112405"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-cp9v-662q-vvx9</id>
    <title>GHSA-cp9v-662q-vvx9 — Pillow: NULL pointer dereference in Image.merge via an unvalidated band 0</title>
    <updated>2026-10-29T08:38:10.828338+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pillow</p>
<p>### 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.</p>
<p>### Details
The validation loop skips band 0:</p>
<p>- `src/PIL/Image.py:3795` iterates `for band in bands[1:]` and checks mode and size only for those.</p>
<p>For an `I` or `F` image the 8-bit plane `image8` is NULL (only `image32` is set). `ImagingMerge` dereferences `bands[0]-&gt;image8[y]` for the multi-band output modes:</p>
<p>- `src/libImaging/Bands.c:302`, `:311`, `:321`</p>
<p>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:</p>
<p>- `src/PIL/IptcImagePlugin.py:156-160`
- `src/PIL/IptcImagePlugin.py:169` registers the opener with no accept function.</p>
<p>### PoC
```python
from PIL import Image</p>
<p># Band 0 is a single-band "I" 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("I", (4, 4))
Image.merge("RGB", [band0, Image.new("L", (4, 4)), Image.new("L", (4, 4))])
```</p>
<p>Run it:
```
$ python 02_poc.py
Segmentation fault (core dumped)
```</p>
<p>Observed on a source build of commit `3e2ab96`.</p>
<p>Under AddressSanitizer:
```
==ERROR: AddressSanitizer…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-cp9v-662q-vvx9"/>
  </entry>
</feed>
