GitHub Advisoryadvisory · PyPI

GHSA-wqw6-wpr3-45rh fpdf2: Exponential SVG '<use>' expansion causes CPU and memory exhaustion in 'FPDF.image()'

MEDIUM Published 2026-10-27 Modified 2026-10-27 Official page ↗
Aliases
CVE-2026-114610
Ecosystem
PyPI
Packages
fpdf2
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400
Reviewed
2026-10-27

Affected packages

• PyPI fpdf2: >= 2.5.0, < 2.8.8 → fixed in 2.8.8

Description

Summary fpdf2 expands SVG `` 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. 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`. Details 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. When fpdf2 resolves an SVG reference, `SVGObject.build_xref()` passes the referenced object to `GraphicsContext.add_item()`: ```python pdf_group.add_item(self.cross_references[ref]) ``` `GraphicsContext.add_item()` uses `clone=True` by default and deep-copies the object: ```python def add_item(self, item, clone=True): if clone: item = deepcopy(item) self.path_items.append(item) ``` 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 `8^n`. `ResourceAccessPolicy` does not prevent this behavior because the SVG contains only inline objects and does not request any external resource. The same failure was reproduced on development commit `a3307f96a0d165831029b3fb644aee5a7ca03328` with `ResourceAccessPolicy.NONE`. PoC This was tested on Linux with Python 3.13.5. The script applies a 128 MB address-space limit so the process fails safely instead of consuming all available system memory. ```python import resource import time from fpdf import FPDF groups = [''] for level in range(1, 6): uses = f'' * 8 groups.append(f'{uses}') svg = ( '' '' + "".join(groups) + '' ).encode() pdf = FPDF() pdf.add_page() limit = 128 * 1024 * 1024 resource.setrlimit(resource.RLIMIT_AS, (limit, limit)) print(f"payload size: {len(svg)} bytes") started = time.perf_counter() try: pdf.image(svg, w=10) except MemoryError: elapsed = time.perf_counter() - started max_rss = resource.getrusage(resource.RUSAGE_SELF).ru_maxrss print(f"MemoryError after {elapsed:.3f}s, max RSS: {max_rss} KiB") ``` ```text payload size: 895 bytes MemoryError after 14.336s, max RSS: 115596 KiB ``` Execution time varies by machine, but the process should show heavy resource use and fail at the configured memory limit. Impact This is an uncontrolled resource consumption vulnerability affecting applications that pass user-controlled SVG data to `FPDF.image()`. A single crafted image can occupy a PDF generation worker for several seconds and then make the current job fail with `MemoryError`. Submitting the same input concurrently repeats the CPU and memory cost across the available workers, reducing or exhausting the service's PDF generation capacity. The payload is less than 1 KB and requires no external resource access, XML entities, special network configuration, or permissive fpdf2 settings.

Related

Alias · CVE (1)

  • CVE-2026-114610 fpdf2 is a PDF creation library for Python. vulnerability

Weakness · CWE (1)

  • CWE-400 Uncontrolled Resource Consumption weakness

References