fix: bump cryptography to ~=50.0 for CVE-2026-69247 - #707
Merged
Conversation
Force a patch release (10.1.1) to ship the cryptography 50.0 upgrade that landed in #706 as a chore commit, which release-please does not release on its own. CVE-2026-69247 / GHSA-g6cj-pr64-35w5: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle. Affects cryptography >=44.0.0,<50.0.0, fixed in 50.0.0. Release-As: 10.1.1
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
1 participant
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
cryptography50.0 upgrade that landed in fix: bump cryptography to ~=50.0 #706.chore:commit, which release-please does not release on its own; thisfix:commit with aRelease-As: 10.1.1trailer forces the patch bump.cryptography >=44.0.0,<50.0.0, fixed in 50.0.0).mainvia fix: bump cryptography to ~=50.0 #706, so this commit is intentionally empty — it exists only to trigger the release.