Bump cryptography to 50.0.0 in uv.lock - #224
Merged
Merged
Conversation
cryptography 49.0.0 has a Bleichenbacher oracle in PKCS#7 EnvelopedData decryption (GHSA-g6cj-pr64-35w5 / PYSEC-2026-3552), which fails `uv audit --locked` in CI. 50.0.0 fixes it. It is a dev-only transitive dependency (twine -> keyring -> secretstorage -> cryptography), so no runtime dependency changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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.
Bumps
cryptographyfrom 49.0.0 to 50.0.0 inuv.lock.49.0.0 is affected by GHSA-g6cj-pr64-35w5 / PYSEC-2026-3552: PKCS#7
EnvelopedDatadecryption exposes a Bleichenbacher oracle through distinguishable errors and timing. This fails theuv audit --lockedstep in theuv-auditworkflow, which runs daily againstmaster. 50.0.0 fixes it.cryptographyis a dev-only transitive dependency (twine->keyring->secretstorage->cryptography), so it is not part of the runtime dependency set. Dependabot's groupeduvversion updates only bump direct dependencies, which is why this needed a manual relock:The diff is limited to the
cryptographyversion and its wheel URLs and hashes. No other locked package changed.Verification:
uv audit --lockedreports no known vulnerabilities for Python 3.10, 3.11, 3.12, and 3.13 (theuv-auditmatrix)uv sync --locked --all-extrassucceeds, so the lockfile is in sync withpyproject.toml🤖 Generated with Claude Code