<?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 22:41:58 +0000</lastBuildDate>
    <item>
      <title>BIT-pillow-2026-96643 — Pillow: PNG eXIf chunk makes EXIF parsing run in quadratic time</title>
      <link>https://cve.radiocsirt.org/vuln/bit-pillow-2026-96643</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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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-96643</guid>
    </item>
    <item>
      <title>BREW-aider-CVE-2026-96643 — Pillow: PNG eXIf chunk makes EXIF parsing run in quadratic time</title>
      <link>https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-96643</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: aider&lt;/p&gt;
&lt;p&gt;### Summary
  A PNG file with a large eXIf chunk full of repeated 6-byte markers makes Pillow&amp;#39;s EXIF parser take seconds of CPU instead of milliseconds. The cost grows with the square of the chunk size, so a normal small-photo-sized file is enough to cause real delay.&lt;/p&gt;
&lt;p&gt;### Details
  `Exif.load()` in `src/PIL/Image.py` strips a marker from the start of the EXIF data like this:&lt;/p&gt;
&lt;p&gt;```python
  while data and data.startswith(b&amp;#34;Exif\x00\x00&amp;#34;):
      data = data[6:]
  ```&lt;/p&gt;
&lt;p&gt;Each pass makes a new copy of the remaining data. A real camera writes this marker once, so this is not normally a problem.&lt;/p&gt;
&lt;p&gt;`chunk_eXIf()` in `src/PIL/PngImagePlugin.py` puts the raw PNG eXIf chunk straight into `info[&amp;#34;exif&amp;#34;]` with no size limit and no check of its content. PNG text chunks (tEXt, zTXt, iTXt) are capped with `MAX_TEXT_CHUNK` and `MAX_TEXT_MEMORY`. The eXIf chunk has no such cap.&lt;/p&gt;
&lt;p&gt;If the eXIf chunk is filled with repeated `Exif\x00\x00` markers instead of real EXIF data, the strip loop runs once per marker, copying a large buffer each time. This is a classic quadratic time bug.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
  This builds a small PNG in memory and times `Image.open().getexif()` on it. No external file needed.&lt;/p&gt;
&lt;p&gt;```python
  import time
  from io import BytesIO
  from PIL import Image, PngImagePlugin&lt;/p&gt;
&lt;p&gt;def chunk(cid, *data):
      fp = BytesIO()
      PngImagePlugin.putchunk(fp, cid, *data)
      return fp.getvalue()&lt;/p&gt;
&lt;p&gt;MAGIC = PngImagePlugin._MAGIC
  IHDR = chunk(b&amp;#34;IHDR&amp;#34;, PngImagePlugin.o32(1…&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
  A PNG file with a large eXIf chunk full of repeated 6-byte markers makes Pillow&amp;#39;s EXIF parser take seconds of CPU instead of milliseconds. The cost grows with the square of the chunk size, so a normal small-photo-sized file is enough to cause real delay.&lt;/p&gt;
&lt;p&gt;### Details
  `Exif.load()` in `src/PIL/Image.py` strips a marker from the start of the EXIF data like this:&lt;/p&gt;
&lt;p&gt;```python
  while data and data.startswith(b&amp;#34;Exif\x00\x00&amp;#34;):
      data = data[6:]
  ```&lt;/p&gt;
&lt;p&gt;Each pass makes a new copy of the remaining data. A real camera writes this marker once, so this is not normally a problem.&lt;/p&gt;
&lt;p&gt;`chunk_eXIf()` in `src/PIL/PngImagePlugin.py` puts the raw PNG eXIf chunk straight into `info[&amp;#34;exif&amp;#34;]` with no size limit and no check of its content. PNG text chunks (tEXt, zTXt, iTXt) are capped with `MAX_TEXT_CHUNK` and `MAX_TEXT_MEMORY`. The eXIf chunk has no such cap.&lt;/p&gt;
&lt;p&gt;If the eXIf chunk is filled with repeated `Exif\x00\x00` markers instead of real EXIF data, the strip loop runs once per marker, copying a large buffer each time. This is a classic quadratic time bug.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
  This builds a small PNG in memory and times `Image.open().getexif()` on it. No external file needed.&lt;/p&gt;
&lt;p&gt;```python
  import time
  from io import BytesIO
  from PIL import Image, PngImagePlugin&lt;/p&gt;
&lt;p&gt;def chunk(cid, *data):
      fp = BytesIO()
      PngImagePlugin.putchunk(fp, cid, *data)
      return fp.getvalue()&lt;/p&gt;
&lt;p&gt;MAGIC = PngImagePlugin._MAGIC
  IHDR = chunk(b&amp;#34;IHDR&amp;#34;, PngImagePlugin.o32(1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-aider-cve-2026-96643</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-NX80742 — Pillow is a Python imaging library</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-nx80742</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-nx80742</guid>
    </item>
    <item>
      <title>EUVD-2026-391813</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391813</link>
      <description>EUVD-2026-391813</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391813</guid>
    </item>
    <item>
      <title>fkie_cve-2026-96643</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-96643</link>
      <description>&lt;p&gt;Pillow is a Python imaging library. From 11.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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-96643</guid>
    </item>
    <item>
      <title>GHSA-g4qv-2jxx-769h — Pillow: PNG eXIf chunk makes EXIF parsing run in quadratic time</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g4qv-2jxx-769h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Pillow&lt;/p&gt;
&lt;p&gt;### Summary
  A PNG file with a large eXIf chunk full of repeated 6-byte markers makes Pillow&amp;#39;s EXIF parser take seconds of CPU instead of milliseconds. The cost grows with the square of the chunk size, so a normal small-photo-sized file is enough to cause real delay.&lt;/p&gt;
&lt;p&gt;### Details
  `Exif.load()` in `src/PIL/Image.py` strips a marker from the start of the EXIF data like this:&lt;/p&gt;
&lt;p&gt;```python
  while data and data.startswith(b&amp;#34;Exif\x00\x00&amp;#34;):
      data = data[6:]
  ```&lt;/p&gt;
&lt;p&gt;Each pass makes a new copy of the remaining data. A real camera writes this marker once, so this is not normally a problem.&lt;/p&gt;
&lt;p&gt;`chunk_eXIf()` in `src/PIL/PngImagePlugin.py` puts the raw PNG eXIf chunk straight into `info[&amp;#34;exif&amp;#34;]` with no size limit and no check of its content. PNG text chunks (tEXt, zTXt, iTXt) are capped with `MAX_TEXT_CHUNK` and `MAX_TEXT_MEMORY`. The eXIf chunk has no such cap.&lt;/p&gt;
&lt;p&gt;If the eXIf chunk is filled with repeated `Exif\x00\x00` markers instead of real EXIF data, the strip loop runs once per marker, copying a large buffer each time. This is a classic quadratic time bug.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
  This builds a small PNG in memory and times `Image.open().getexif()` on it. No external file needed.&lt;/p&gt;
&lt;p&gt;```python
  import time
  from io import BytesIO
  from PIL import Image, PngImagePlugin&lt;/p&gt;
&lt;p&gt;def chunk(cid, *data):
      fp = BytesIO()
      PngImagePlugin.putchunk(fp, cid, *data)
      return fp.getvalue()&lt;/p&gt;
&lt;p&gt;MAGIC = PngImagePlugin._MAGIC
  IHDR = chunk(b&amp;#34;IHDR&amp;#34;, PngImagePlugin.o32(1…&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 PNG file with a large eXIf chunk full of repeated 6-byte markers makes Pillow&amp;#39;s EXIF parser take seconds of CPU instead of milliseconds. The cost grows with the square of the chunk size, so a normal small-photo-sized file is enough to cause real delay.&lt;/p&gt;
&lt;p&gt;### Details
  `Exif.load()` in `src/PIL/Image.py` strips a marker from the start of the EXIF data like this:&lt;/p&gt;
&lt;p&gt;```python
  while data and data.startswith(b&amp;#34;Exif\x00\x00&amp;#34;):
      data = data[6:]
  ```&lt;/p&gt;
&lt;p&gt;Each pass makes a new copy of the remaining data. A real camera writes this marker once, so this is not normally a problem.&lt;/p&gt;
&lt;p&gt;`chunk_eXIf()` in `src/PIL/PngImagePlugin.py` puts the raw PNG eXIf chunk straight into `info[&amp;#34;exif&amp;#34;]` with no size limit and no check of its content. PNG text chunks (tEXt, zTXt, iTXt) are capped with `MAX_TEXT_CHUNK` and `MAX_TEXT_MEMORY`. The eXIf chunk has no such cap.&lt;/p&gt;
&lt;p&gt;If the eXIf chunk is filled with repeated `Exif\x00\x00` markers instead of real EXIF data, the strip loop runs once per marker, copying a large buffer each time. This is a classic quadratic time bug.&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
  This builds a small PNG in memory and times `Image.open().getexif()` on it. No external file needed.&lt;/p&gt;
&lt;p&gt;```python
  import time
  from io import BytesIO
  from PIL import Image, PngImagePlugin&lt;/p&gt;
&lt;p&gt;def chunk(cid, *data):
      fp = BytesIO()
      PngImagePlugin.putchunk(fp, cid, *data)
      return fp.getvalue()&lt;/p&gt;
&lt;p&gt;MAGIC = PngImagePlugin._MAGIC
  IHDR = chunk(b&amp;#34;IHDR&amp;#34;, PngImagePlugin.o32(1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g4qv-2jxx-769h</guid>
    </item>
    <item>
      <title>PYSEC-2026-4342</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-4342</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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. This issue is fixed in version 13.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-4342</guid>
    </item>
    <item>
      <title>RHSA-2026:92510 — Red Hat Security Advisory: RHOAI 3.4.6 - Red Hat OpenShift AI</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:92510</link>
      <description>&lt;p&gt;sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 RHOAI MaaS: llm-d: MaaS/llm-d inference Gateway: default allowedRoutes.namespaces.from: All allows namespace users to hijack shared model-serving traffic (tokens, prompts, outputs) fast-uri: Fast-uri: Security policy bypass due to URL parsing inconsistency github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service due to integer overflow in SSH channel write github.com/open-telemetry/opentelemetry-go: go.opentelemetry.io/otel/baggage: go.opentelemetry.io/otel/propagation: OpenTelemetry-Go:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 RHOAI MaaS: llm-d: MaaS/llm-d inference Gateway: default allowedRoutes.namespaces.from: All allows namespace users to hijack shared model-serving traffic (tokens, prompts, outputs) fast-uri: Fast-uri: Security policy bypass due to URL parsing inconsistency github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority golang.org/x/net/html: golang.org/x/net/html: Arbitrary code execution via Cross-Site Scripting cryptography: cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang.org/x/crypto/ssh: golang: golang.org/x/crypto/ssh: Denial of Service due to integer overflow in SSH channel write github.com/open-telemetry/opentelemetry-go: go.opentelemetry.io/otel/baggage: go.opentelemetry.io/otel/propagation: OpenTelemetry-Go:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:92510</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-96643</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-96643</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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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.0.0 until 13.0.0, Exif.load() in src/PIL/Image.py repeatedly slices the remaining EXIF data while it begins with the six-byte Exif header. src/PIL/PngImagePlugin.py accepts an uncapped PNG eXIf chunk, so a file filled with repeated headers causes a new shrinking copy on every iteration and quadratic CPU work. The condition is reachable through Image.getexif(), Image._getexif(), and ImageOps.exif_transpose(), including common photo-upload rotation workflows. 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-96643</guid>
    </item>
  </channel>
</rss>
