Advisory record · GHSA-jfx9-29x2-rv3j

pypdf can exhaust RAM via manipulated LZWDecode streams

CVSS 6.6 MediumEPSS 0.0044 · 38th percentile

Published by the GitHub Advisory Database at 22 Oct 2025, 19:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pypdfPyPI<6.1.36.1.3
Identifiers
GHSA-jfx9-29x2-rv3j · CVE-2025-62708 · PYSEC-2026-1831
Weakness (CWE)
CWE-409
Published
22 Oct 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

pypdf versions before 6.1.3 can be made to use large amounts of memory. An attacker who supplies a crafted PDF can trigger this when the content stream of a page using the LZWDecode filter is parsed, so a user opening or processing such a file is affected. Upgrade to pypdf 6.1.3 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.6 Medium 4.0 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/E:U CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0044, the 38th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 22 Oct 2025, 22:15 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:34 UTC First seen by agentprime
  3. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.