<?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-11-17T14:43:42.414748+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-keeper-commander-cve-2026-114610</id>
    <title>BREW-keeper-commander-CVE-2026-114610 — fpdf2: Exponential SVG '&lt;use&gt;' expansion causes CPU and memory exhaustion in 'FPDF.image()'</title>
    <updated>2026-11-17T14:43:42.418367+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: keeper-commander</p>
<p>### Summary</p>
<p>fpdf2 expands SVG `&lt;use&gt;` references by deep-copying the complete referenced graphics tree. A small SVG can use nested references to make the number of in-memory objects grow exponentially, causing excessive CPU and memory consumption during `FPDF.image()` processing.</p>
<p>This was reproduced with an 895-byte SVG on fpdf2 2.8.7. Under a 128 MB process limit, the input kept the process busy for about 14 seconds before raising `MemoryError`.</p>
<p>### Details</p>
<p>The issue is in fpdf2's own SVG reference handling. It does not rely on XML entities, external URLs, local files, or vulnerable behavior in another dependency.</p>
<p>When fpdf2 resolves an SVG reference, [`SVGObject.build_xref()`](https://github.com/py-pdf/fpdf2/blob/a3307f96a0d165831029b3fb644aee5a7ca03328/fpdf/svg.py#L1584) passes the referenced object to `GraphicsContext.add_item()`:</p>
<p>```python
pdf_group.add_item(self.cross_references[ref])
```</p>
<p>[`GraphicsContext.add_item()`](https://github.com/py-pdf/fpdf2/blob/a3307f96a0d165831029b3fb644aee5a7ca03328/fpdf/drawing.py#L3618-L3633) uses `clone=True` by default and deep-copies the object:</p>
<p>```python
def add_item(self, item, clone=True):
    if clone:
        item = deepcopy(item)
    self.path_items.append(item)
```</p>
<p>An attacker can define `g1` as eight references to `g0`, `g2` as eight references to `g1`, and so on. Each level adds only a small amount of XML, but fpdf2 copies the entire tree from the previous level eight times. The resulting work grows approximately as…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-keeper-commander-cve-2026-114610"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-114610</id>
    <title>CVE-2026-114610 — fpdf2: Exponential SVG '&lt;use&gt;' expansion causes CPU and memory exhaustion in 'FPDF.image()'</title>
    <updated>2026-11-17T14:43:42.418448+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> py-pdf fpdf2</p>
<p>fpdf2 is a PDF creation library for Python. From 2.5.0 until 2.8.8, fpdf2's SVGObject.build_xref() passes nested SVG &lt;use&gt; references to GraphicsContext.add_item(), whose default clone=True deep-copy behavior copies the complete referenced graphics tree during FPDF.image() processing. Repeating references at each nesting level makes the in-memory object count and processing work grow exponentially, allowing a small user-controlled SVG to consume excessive CPU and memory, raise MemoryError, fail PDF generation jobs, and reduce or exhaust worker capacity. ResourceAccessPolicy does not prevent the issue because the references are inline and require no external resource, XML entity, local file, or permissive network setting. This issue is fixed in version 2.8.8.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-114610"/>
  </entry>
</feed>
