Quick answers
- Is CVE-2026-102995 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102995 being exploited in the wild.
- How severe is CVE-2026-102995?
- High severity, with a CVSS score of 4, published 30 September 2026.
- Which products and versions are affected?
- Py-Pdf Pypdf prior to 6.18.1; pypdf (PyPI) < 6.18.1, ECOSYSTEM:introduced=0,fixed=6.18.1.
- Is there a fix for CVE-2026-102995?
- Yes. pypdf (PyPI): upgrade to 6.18.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102995 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-102995?
- Check whether you run Py-Pdf Pypdf or pypdf (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pypdf (PyPI): upgrade to 6.18.1 or later
pip install "pypdf>=6.18.1"
Technical details
The vulnerability exists in pypdf/_cmap.py's parse_bfchar function, which fails to properly limit the length of tokens decoded from PDF font /ToUnicode mappings. An attacker can craft a PDF with oversized source-code or destination-string tokens that cause the parser to retain excessive memory. The flaw is triggered during PDF parsing without requiring user interaction beyond opening the file.
Affected products
- py-pdf pypdf prior to 6.18.1
Identifiers
- CVE-2026-102995
- GHSA-fp3h-c4fm-7vvf
- PYSEC-2026-4154
Timeline
- 2026-09-30: disclosed
- 2026-09-11: patched