<?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>Sun, 25 Oct 2026 18:28:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-112397 — Pillow: Out-of-bounds access in _imagingmorph on a zero-width image</title>
      <link>https://db.gcve.eu/vuln/cve-2026-112397</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. Prior to 13.0.0, Pillow&amp;#39;s ImageMorph.MorphOp.apply() can access memory before a row buffer for a zero-width image. PPM and PGM input can create an image with width zero, and the native morphology routine indexes outrow[width - 1] without rejecting that geometry. An attacker can supply such an image to an application that applies a morphology operation. This can crash the process. 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. Prior to 13.0.0, Pillow&amp;#39;s ImageMorph.MorphOp.apply() can access memory before a row buffer for a zero-width image. PPM and PGM input can create an image with width zero, and the native morphology routine indexes outrow[width - 1] without rejecting that geometry. An attacker can supply such an image to an application that applies a morphology operation. This can crash the process. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-112397</guid>
    </item>
    <item>
      <title>GHSA-58r4-6rv3-gfh8 — Pillow: Out-of-bounds access in _imagingmorph on a zero-width image</title>
      <link>https://db.gcve.eu/vuln/ghsa-58r4-6rv3-gfh8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Pillow&lt;/p&gt;
&lt;p&gt;### Summary
A PPM or PGM file can declare a width of 0, which Pillow accepts, producing an image of size `(0, N)`. Passing that image to `ImageMorph.MorphOp.apply()` makes the native morphology code index a row buffer at `outrow[width - 1]`, which is `outrow[-1]` when the width is 0. The process crashes.&lt;/p&gt;
&lt;p&gt;### Details
The PPM parser reads width and height with no lower-bound check:&lt;/p&gt;
&lt;p&gt;- `src/PIL/PpmImagePlugin.py:119`&lt;/p&gt;
&lt;p&gt;The native `apply()` writes the row edges with no guard that the width is positive:&lt;/p&gt;
&lt;p&gt;- `src/_imagingmorph.c:81` sets `outrow[0] = outrow[width - 1] = 0;`&lt;/p&gt;
&lt;p&gt;`match()` and `get_on_pixels()` use the same edge-indexing pattern.&lt;/p&gt;
&lt;p&gt;### PoC
```python
from PIL import Image, ImageMorph&lt;/p&gt;
&lt;p&gt;# A width-0 image (also producible from a crafted PPM header). apply() indexes
# outrow[width - 1] == outrow[-1] in native code.
im = Image.new(&amp;#34;L&amp;#34;, (0, 5))
ImageMorph.MorphOp(op_name=&amp;#34;dilation4&amp;#34;).apply(im)
```&lt;/p&gt;
&lt;p&gt;Run it:
```
$ python 03_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: SEGV on unknown address (pc ... in apply)
    #0 apply   src/_imagingmorph.c:81
SUMMARY: AddressSanitizer: SEGV src/_imagingmorph.c:81 in apply
```
With width 0 the `outrow[width - 1]` write lands on an unmapped page, so it surfaces as a SEGV pinned to the edge-write line rather than a redzone overflow.&lt;/p&gt;
&lt;p&gt;### Impact
Out-of-bounds write in a C extension. Affects any application that runs a morphology operation on an…&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
A PPM or PGM file can declare a width of 0, which Pillow accepts, producing an image of size `(0, N)`. Passing that image to `ImageMorph.MorphOp.apply()` makes the native morphology code index a row buffer at `outrow[width - 1]`, which is `outrow[-1]` when the width is 0. The process crashes.&lt;/p&gt;
&lt;p&gt;### Details
The PPM parser reads width and height with no lower-bound check:&lt;/p&gt;
&lt;p&gt;- `src/PIL/PpmImagePlugin.py:119`&lt;/p&gt;
&lt;p&gt;The native `apply()` writes the row edges with no guard that the width is positive:&lt;/p&gt;
&lt;p&gt;- `src/_imagingmorph.c:81` sets `outrow[0] = outrow[width - 1] = 0;`&lt;/p&gt;
&lt;p&gt;`match()` and `get_on_pixels()` use the same edge-indexing pattern.&lt;/p&gt;
&lt;p&gt;### PoC
```python
from PIL import Image, ImageMorph&lt;/p&gt;
&lt;p&gt;# A width-0 image (also producible from a crafted PPM header). apply() indexes
# outrow[width - 1] == outrow[-1] in native code.
im = Image.new(&amp;#34;L&amp;#34;, (0, 5))
ImageMorph.MorphOp(op_name=&amp;#34;dilation4&amp;#34;).apply(im)
```&lt;/p&gt;
&lt;p&gt;Run it:
```
$ python 03_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: SEGV on unknown address (pc ... in apply)
    #0 apply   src/_imagingmorph.c:81
SUMMARY: AddressSanitizer: SEGV src/_imagingmorph.c:81 in apply
```
With width 0 the `outrow[width - 1]` write lands on an unmapped page, so it surfaces as a SEGV pinned to the edge-write line rather than a redzone overflow.&lt;/p&gt;
&lt;p&gt;### Impact
Out-of-bounds write in a C extension. Affects any application that runs a morphology operation on an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-58r4-6rv3-gfh8</guid>
    </item>
  </channel>
</rss>
