pypdf: Manipulated XMP metadata streams can exhaust RAM

When

2026-06-16 13:45 UTC

Where

Global (internet)

Category

cyber_advisory · pip

### Impact An attacker who uses this vulnerability can craft a PDF which leads to large memory usage. This requires parsing large XMP metadata, possibly with lots of unnecessary elements. ### Patches This has been fixed in [pypdf==6.12.1](https://github.com/py-pdf/pypdf/releases/tag/6.12.1). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#3796](https://github.com/py-pdf/pypdf/pull/3796).

Sources

• GitHub Advisory Database ↗ · first seen 2026-06-16 13:45 UTC

Defaxon links out to the original reporting and never republishes article text.

Correlated events

Computed by the Defaxon correlation engine — linked by shared actors, co-location, and temporal proximity. Scored hypotheses, never causal claims.

• pypdf: Possible large memory usage for form XObjects during text extraction
  Shared actorsInvolves pip/pypdf, pip/pypdf· 82% match
• pypdf: Inefficient decoding of FlateDecode PNG predictor streams
  Shared actorsInvolves pip/pypdf, pip/pypdf· 82% match
• pypdf: Possible infinite loop when retrieving fonts for layout-mode text extraction
  Shared actorsInvolves pip/pypdf, pip/pypdf· 82% match
• pypdf: Possible infinite loop when processing outlines/bookmarks in writer
  Shared actorsInvolves pip/pypdf, pip/pypdf· 82% match

← Back to the live map