pypdf: Possible infinite loop when processing outlines/bookmarks in writer

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps pypdf (pip), pypdf (pypi). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for pypdf, pypdf.
2. 2Review the reported fix. Update pypdf to 6.13.0; pypdf to 6.13.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jun 16, 2026

   Evidence: source:osv:source_dates:source-dates:record

2. Source modified

   Sep 10, 2026

   Evidence: source:osv:source_dates:source-dates:record

3. First seen by HOL

   Jun 19, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• djust's Django model serialization has no sensitive-field denylist: password hashes, privilege flags, and PII on a public view attribute are sent to the clientSame pip ecosystem
• djust: WebSocket/runtime reconstructed request omits the client Host, causing host/subdomain TenantResolvers to misresolve the tenant on the live pathSame pip ecosystem
• djust: Unsigned client state snapshot is restored as trusted view state (privilege escalation / state injection)Same pip ecosystem
• djust: SSE sessions are not bound to the authenticated user; the client-chosen session_id is the sole authorization capability (session hijack)Same pip ecosystem
• djust has an authorization bypass on the WebSocket/SSE mount pathSame pip ecosystem
• djust has broken object-level access control (IDOR)Same pip ecosystem