LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24688: pypdf has possible Infinite Loop when processing outlines/bookmarks

pypdf is a free and open-source pure-python PDF library. An attacker who uses an infinite loop vulnerability that is present in versions prior to 6.6.2 can craft a PDF which leads to an infinite loop. This requires accessing the outlines/bookmarks. This has been fixed in pypdf 6.6.2. If projects cannot upgrade yet, consider applying the changes from PR #3610 manually.

MediumCVSS 5.1Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24688 affects pypdf, a Python PDF library. Versions before 6.6.2 can enter an infinite loop when processing a specially crafted PDF’s outlines or bookmarks. The likely business impact is resource exhaustion or stalled processing in systems that inspect PDF bookmarks. The vendor fixed it in pypdf 6.6.2.

Executive priority

Treat as a routine but timely denial-of-service fix. Prioritize internet-facing or customer-facing PDF workflows that parse bookmarks, because a crafted file could tie up processing. This is not currently evidenced as exploited in the wild and does not indicate data compromise.

Technical view

The issue is CWE-835: loop with unreachable exit condition. A crafted PDF can trigger an infinite loop in pypdf before 6.6.2 when application code accesses outlines/bookmarks. The CVE lists CVSS 4.0 score 5.1, with low availability impact and no confidentiality or integrity impact. PR #3610 and commit b1282f8 are associated with the fix.

Likely exposure

Exposure is most likely in Python applications or services using pypdf below 6.6.2 and reading PDF outlines/bookmarks from untrusted or user-supplied files. Systems that only store PDFs or do not access bookmarks may have lower practical exposure, based on the advisory description.

Exploitation context

The sources describe crafted-PDF triggering but do not cite active exploitation, public weaponization, or KEV listing. Exploitation requires the vulnerable application to process the malicious PDF and access outlines/bookmarks. The expected effect is denial of service through an infinite loop, not data theft or code execution.

Researcher notes

Key scoping condition is outline/bookmark access. The CVE record’s CVSS vector reports local attack vector despite the crafted-file scenario, so assess deployment context carefully. Sources name pypdf versions before 6.6.2 as affected and identify 6.6.2, PR #3610, and commit b1282f8 as the fix path.

Mitigation direction

  • Upgrade pypdf to version 6.6.2 or later.
  • If upgrade is blocked, review applying PR #3610 changes manually.
  • Prioritize services processing untrusted PDFs and reading outlines or bookmarks.
  • Monitor vendor advisory and release notes for any follow-up guidance.

Validation and detection

  • Inventory Python applications that depend on pypdf.
  • Confirm installed pypdf versions are 6.6.2 or later.
  • Identify code paths that access PDF outlines or bookmarks.
  • Review PDF-processing services accepting user-supplied or external files.
  • Verify dependency lockfiles and deployed environments reflect the fixed version.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-835: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24688 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.1CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

5.1Medium
CVSS 4.0 vector shape for CVE-2026-24688Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
py-pdfpypdf< 6.6.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-835 · source CWE mapping

Loop with Unreachable Exit Condition ('Infinite Loop')

Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.