CVE-2026-48735 Details
Description
pypdf is a free and open-source pure-python PDF library. Prior to 6.12.1, 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. This vulnerability is fixed in 6.12.1.
A memory exhaustion vulnerability has been identified in pypdf versions prior to 6.12.1. This issue arises when the library parses large XMP metadata streams, which can include excessive elements, leading to significant memory consumption. An attacker can exploit this vulnerability by crafting a PDF that takes advantage of the problematic metadata handling.
Users can upgrade to pypdf version 6.12.1 or later to address this vulnerability. If an immediate upgrade is not possible, the changes from pull request #3796 can be applied as a temporary workaround.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 2, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/py-pdf/pypdf/pull/3796 | [email protected] | Issue TrackingPatch |
| https://github.com/py-pdf/pypdf/releases/tag/6.12.1 | [email protected] | Release Notes |
| https://github.com/py-pdf/pypdf/security/advisories/GHSA-wjqc-6w8f-h24c | [email protected] | PatchVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-770 | Allocation of Resources Without Limits or Throttling | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| pypdf project pypdf | < 6.12.1 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 29, 2026 | Initial Analysis | [email protected] |
| May 28, 2026 | New CVE Received | [email protected] |