Allow cryptography >=45.0.0,<51.0.0 - #245
Merged
Merged
Conversation
Contributor
Author
|
I had closed the PR when I misread your comments about PRs; reopening now that I understand now that you do accept PRs. Sorry for the confusion on my end! |
dominic-clerk
approved these changes
Aug 11, 2026
Contributor
|
Thank you! |
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
Widen the supported
cryptographyrange to>=45.0.0,<51.0.0, allowing downstream users to install the remediated 50.x release line.Closes #244.
Why
CVE-2026-69247 affects
cryptography >=44.0.0,<50.0.0. The current<49.0.0ceiling prevents downstream users from installing the remediatedcryptography50.x release line.PR #238 is the precedent for raising this ceiling in
.speakeasy/gen.yaml. This change keeps the constraint in.speakeasy/gen.yaml, the Speakeasy source of truth, so the next SDK regeneration propagates it, matching how #238 was done.pyproject.tomlis also updated because the regeneration immediately following #238 synced the previous constraint change there.No generated SDK code is changed.
Validation
Environment setup:
Installed version and full test suite:
The skipped tests are credential-gated. Additional credentialed testing found a pre-existing, order-dependent
test_verify_token_invalid_secret_keyfailure caused by the module-global JWKS cache; it reproduces with bothcryptography48 and 50 and is therefore cryptography-independent. Resetting that cache between tests yields71 passed, 2 skippedwith either version. No test workaround is included here so this PR remains scoped to the dependency bounds. (Root cause and fix are in #246.)The suite includes the JWT/JWKS and request-authentication coverage in
test_verify_token.py,test_authenticate_request.py, andtest_clerk_before_request_hook.py.