<?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://vulnerability.circl.lu</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, 05 Oct 2026 10:01:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-46250 — pypdf possible Infinite Loop when PdfWriter(clone_from) is used with a PDF</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-46250</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; py-pdf pypdf&lt;/p&gt;
&lt;p&gt;pypdf is a free and open-source pure-python PDF library. An attacker who uses a vulnerability present in versions 3.7.0 through 3.16.4 can craft a PDF which leads to an infinite loop. This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage. That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations. The issue was fixed in version 3.17.0. As a workaround, apply the patch manually by modifying `pypdf/generic/_data_structures.py`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; py-pdf pypdf&lt;/p&gt;
&lt;p&gt;pypdf is a free and open-source pure-python PDF library. An attacker who uses a vulnerability present in versions 3.7.0 through 3.16.4 can craft a PDF which leads to an infinite loop. This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage. That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations. The issue was fixed in version 3.17.0. As a workaround, apply the patch manually by modifying `pypdf/generic/_data_structures.py`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-46250</guid>
    </item>
    <item>
      <title>GHSA-wjcc-cq79-p63f — Possible Infinite Loop when PdfWriter(clone_from) is used with a PDF</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wjcc-cq79-p63f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pypdf&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop.
This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage.&lt;/p&gt;
&lt;p&gt;That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations.&lt;/p&gt;
&lt;p&gt;### Patches
The issue was fixed with #2264&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot update your version of pypdf, you should modify `pypdf/generic/_data_structures.py` just like #2264 did.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pypdf&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop.
This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage.&lt;/p&gt;
&lt;p&gt;That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations.&lt;/p&gt;
&lt;p&gt;### Patches
The issue was fixed with #2264&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot update your version of pypdf, you should modify `pypdf/generic/_data_structures.py` just like #2264 did.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wjcc-cq79-p63f</guid>
    </item>
    <item>
      <title>PYSEC-2026-1834 — Possible Infinite Loop when PdfWriter(clone_from) is used with a PDF</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-1834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pypdf&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop.
This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage.&lt;/p&gt;
&lt;p&gt;That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations.&lt;/p&gt;
&lt;p&gt;### Patches
The issue was fixed with #2264&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot update your version of pypdf, you should modify `pypdf/generic/_data_structures.py` just like #2264 did.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pypdf&lt;/p&gt;
&lt;p&gt;### Impact
An attacker who uses this vulnerability can craft a PDF which leads to an infinite loop.
This infinite loop blocks the current process and can utilize a single core of the CPU by 100%. It does not affect memory usage.&lt;/p&gt;
&lt;p&gt;That is, for example, the case when the pypdf-user manipulates an incoming malicious PDF e.g. by merging it with another PDF or by adding annotations.&lt;/p&gt;
&lt;p&gt;### Patches
The issue was fixed with #2264&lt;/p&gt;
&lt;p&gt;### Workarounds
If you cannot update your version of pypdf, you should modify `pypdf/generic/_data_structures.py` just like #2264 did.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-1834</guid>
    </item>
  </channel>
</rss>
