Repository navigation
Raise pypdf floor to 6.21.2 to close known CVEs - #3209
Open
terryozaki-wq wants to merge 1 commit into
Open
terryozaki-wq wants to merge 1 commit into
terryozaki-wq wants to merge 1 commit into
Conversation
pypdf>=6.19.0 still permits resolving vulnerable releases below the fixed 6.21.2 (no lower bound excludes them, e.g. a cached/offline mirror or a transitive upper-bound pin elsewhere could still select one). Raises the floor rather than pinning an exact version, consistent with the rest of this file's unpinned dependency style. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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.
Summary
pypdf>=6.19.0still permits resolving a vulnerable release below the fixed6.21.2— the floor doesn't exclude anything below it, so a cached/offline mirror or a transitive upper-bound constraint elsewhere could still select one.6.21.2rather than pinning an exact version, consistent with the rest ofpyproject.toml's unpinned (>=) dependency style.Context
Found via the same dependency-drift audit that identified the nltk CVE fix in #3202.
devhas no lockfile for this file, so the equivalent fix here is raising the floor.Test plan
pypdf>=6.21.2cleanly🤖 Generated with Claude Code