Skip to content

fix(deps): bump pypdf to 6.21.4 (CVE-2026-119203, 7 advisories) - #595

Open
superbot-helper wants to merge 2 commits into
Unstructured-IO:mainfrom
superbot-helper:security/bump-pypdf-6.21.2
Open

superbot-helper wants to merge 2 commits into
Unstructured-IO:mainfrom
superbot-helper:security/bump-pypdf-6.21.2

Conversation

@superbot-helper

@superbot-helper superbot-helper commented Oct 30, 2026 •

Copy link
Copy Markdown

pypdf resolves to 6.21.4 in uv.lock; pyproject.toml is unchanged.

The branch pinned 6.21.2, which is inside the affected range of 7 published pypdf advisories, all high severity. An OSV query for pypdf@6.21.2 returns those 7 records; the same query for pypdf@6.21.4 returns none. The highest fixed version across the 7 is 6.21.4.

pyproject.toml already declares pypdf >=6.0.0, <7.0.0, which admits 6.21.4, so this is a lockfile-only bump. uv lock --upgrade-package pypdf with uv 0.13.4 — the version the repository's Dockerfile pins (Dockerfile:14) — resolves 6.21.4. The committed diff carries only the resulting pypdf package entry, so the lockfile's existing revision and markers are left as they were; uv lock --check accepts the result.

This bump closes, for this repository, the following advisories affecting 6.21.2:

7 advisories closed by pinning 6.21.4
Severity GHSA CVE Advisory
high GHSA-42gh-23hr-vphw CVE-2026-119206 pypdf has possible long runtimes when retrieving page labels
high GHSA-4vqv-7265-gm2w CVE-2026-119207 pypdf has possible large memory usage for exceptions in strict mode
high GHSA-5849-834g-hvw5 CVE-2026-119203 pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search
high GHSA-62m5-6wh8-28x7 CVE-2026-119208 pypdf has possible long runtimes/large memory usage for encrypted PDF files
high GHSA-cggf-277g-3q54 CVE-2026-119204 pypdf has possible large memory usage when parsing page tree
high GHSA-mfr5-77xh-9j7h CVE-2026-119205 pypdf has possible infinite loop when cloning dictionaries
high GHSA-x3rh-gjgm-fmqc CVE-2026-119209 pypdf has possible large memory usage when parsing cross-reference streams

Verification

  • uv lock --check (uv 0.13.4, the version in Dockerfile:14) exits 0 against the committed lockfile.
  • uv sync --frozen --dry-run resolves the full 173-package graph without installing or executing any package.
  • pyproject.toml is byte-identical to the branch head (sha256 a5180776bc23286d2393f080890ea432eb0e829abb6027df1f75c12c276650b6).
  • No package version in uv.lock changes besides pypdf 6.21.2 → 6.21.4.

GHSA-6c7f-9265-g8fw (CVE-2026-115572): pypdf returns early from its object
cache only when the lookup is not None, and a missing object is cached as
None, so each reference to the same absent object re-copies and re-scans the
whole stream. A 1.2 MB PDF whose page tree references one never-defined object
20,000 times takes about 70 s in the page-tree walk on 6.11.0 and 0.025 s on
6.21.2.

The API image installs exactly this lock with
`uv sync --no-dev --no-install-project --locked`, and _check_pdf runs that
walk on every PDF upload to POST /general/v0/general before the route has any
chance to time out or reject the file. uv.lock only; no source changes.
@socket-security

socket-security Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedpypi/​pypdf@​6.11.0 ⏵ 6.21.499100 +75100100100

View full report

pypdf 6.21.2 is inside the affected range of 7 published advisories;
6.21.4 is the highest fixed version across them and leaves none of the
7 ranges matching. pyproject.toml already admits 6.21.4
(>=6.0.0, <7.0.0), so this is a lockfile-only bump.

Signed-off-by: Superbot Helper <superbot-helper@users.noreply.github.com>
@superbot-helper superbot-helper changed the title Bump pypdf from 6.11.0 to 6.21.2 fix(deps): bump pypdf to 6.21.4 (CVE-2026-119203, 7 advisories) Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant