Skip to main content
VulnerabilityPublished

CVE-2026-119209: Pdfalyzer · pypdf has possible large memory usage when parsing cross-reference streams

Affects pdfalyzerSource GCVE Database

0
Compare
Authoritative record:CVE-2026-119209· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in 6.21.3 : patch pdfalyzer soon.

Data as of 31 Oct 2026, 15:54 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.1
Patch
Available – fixed in 6.21.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Homebrewpdfalyzerpkg:brew/pdfalyzerOther threatsAffected
  • >=1.16.1
Fixed in–

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

AI-suggested

Upgrade to pypdf version 6.21.3 or later to fully remediate this vulnerability. If upgrading is not feasible immediately, apply the code changes from pull request #4269 as a temporary workaround to mitigate the issue.

Description

CVE-2026-119209 is a vulnerability in the pdfalyzer tool (pypdf library) that allows an attacker to craft a PDF file with cross-reference streams causing large memory usage when parsed. This can lead to denial of service due to resource exhaustion. The issue affects versions starting from 1.16.1. A fix is available in pypdf version 6.21.3. If upgrading is not immediately possible, applying the changes from the referenced pull request #4269 is recommended as a workaround.

References

Community reviews

Loading reviews…