Repository navigation
fix(deps): bump pypdf to 6.21.4 (CVE-2026-119203, 7 advisories) - #595
Open
superbot-helper wants to merge 2 commits into
Open
superbot-helper wants to merge 2 commits into
superbot-helper wants to merge 2 commits into
Conversation
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.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pypdfresolves to 6.21.4 inuv.lock;pyproject.tomlis 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.2returns those 7 records; the same query forpypdf@6.21.4returns none. The highest fixed version across the 7 is 6.21.4.pyproject.tomlalready declarespypdf >=6.0.0, <7.0.0, which admits 6.21.4, so this is a lockfile-only bump.uv lock --upgrade-package pypdfwithuv 0.13.4— the version the repository's Dockerfile pins (Dockerfile:14) — resolves 6.21.4. The committed diff carries only the resultingpypdfpackage entry, so the lockfile's existing revision and markers are left as they were;uv lock --checkaccepts the result.This bump closes, for this repository, the following advisories affecting 6.21.2:
7 advisories closed by pinning 6.21.4
Verification
uv lock --check(uv 0.13.4, the version inDockerfile:14) exits 0 against the committed lockfile.uv sync --frozen --dry-runresolves the full 173-package graph without installing or executing any package.pyproject.tomlis byte-identical to the branch head (sha256a5180776bc23286d2393f080890ea432eb0e829abb6027df1f75c12c276650b6).uv.lockchanges besidespypdf6.21.2 → 6.21.4.