Skip to main content
VulnerabilityPublished Updated

CVE-2026-102996: pypdf · Possible large memory usage when parsing font data

Affects psutilsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-102996· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 3.3.17_1 soon.

Data as of 1 Nov 2026, 00:09 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.3.17_1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade psutils to 3.3.17_1.

Affected software

ProductAffectedFixed in
Homebrewpsutilspkg:brew/psutilsOther threatsAffected
  • >=3.0 <3.3.17_1
Fixed in
  • 3.3.17_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Impact An attacker who uses this vulnerability can craft a PDF which leads to large memory consumption. This requires parsing the `/Widths` entry of a TrueType or Type1 fonts with unusually large values, for example during text extraction. ### Patches This has been fixed in [pypdf==6.18.1](https://github.com/py-pdf/pypdf/releases/tag/6.18.1). ### Workarounds If you cannot upgrade yet, consider applying the changes from PR [#4072](https://github.com/py-pdf/pypdf/pull/4072).

References

Community reviews

Loading reviews…