<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T12:22:41.448759+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/brew-pdfalyzer-cve-2026-31826</id>
    <title>BREW-pdfalyzer-CVE-2026-31826 — pypdf: manipulated stream length values can exhaust RAM</title>
    <updated>2026-10-02T12:22:41.452009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: pdfalyzer</p>
<p>### Impact</p>
<p>An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing a content stream with a rather large `/Length` value, regardless of the actual data length inside the stream.</p>
<p>### Patches
This has been fixed in [pypdf==6.8.0](https://github.com/py-pdf/pypdf/releases/tag/6.8.0).</p>
<p>### Workarounds
If you cannot upgrade yet, consider applying the changes from PR [#3675](https://github.com/py-pdf/pypdf/pull/3675).</p>
<p>As far as we are aware, this mostly affects reading from buffers of unknown size, as returned by `open("file.pdf", mode="rb")` for example. Passing a file path or a `BytesIO` buffer to *pypdf* instead does not seem to trigger the vulnerability.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-pdfalyzer-cve-2026-31826"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-31826</id>
    <title>CVE-2026-31826 — pypdf: manipulated stream length values can exhaust RAM</title>
    <updated>2026-10-02T12:22:41.452061+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> py-pdf pypdf</p>
<p>pypdf is a free and open-source pure-python PDF library. Prior to 6.8.0, an attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing a content stream with a rather large /Length value, regardless of the actual data length inside the stream. This vulnerability is fixed in 6.8.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-31826"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hqmh-ppp3-xvm7</id>
    <title>GHSA-hqmh-ppp3-xvm7 — pypdf: manipulated stream length values can exhaust RAM</title>
    <updated>2026-10-02T12:22:41.452090+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: pypdf</p>
<p>### Impact</p>
<p>An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing a content stream with a rather large `/Length` value, regardless of the actual data length inside the stream.</p>
<p>### Patches
This has been fixed in [pypdf==6.8.0](https://github.com/py-pdf/pypdf/releases/tag/6.8.0).</p>
<p>### Workarounds
If you cannot upgrade yet, consider applying the changes from PR [#3675](https://github.com/py-pdf/pypdf/pull/3675).</p>
<p>As far as we are aware, this mostly affects reading from buffers of unknown size, as returned by `open("file.pdf", mode="rb")` for example. Passing a file path or a `BytesIO` buffer to *pypdf* instead does not seem to trigger the vulnerability.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hqmh-ppp3-xvm7"/>
  </entry>
</feed>
