Upgrade cryptography to resolve GHSA-537c-gmf6-5ccf - #487
Merged
Conversation
cigamit
approved these changes
Jun 17, 2026
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
Upgrades
cryptographyfrom 46.0.7 to 49.0.0 to resolve GHSA-537c-gmf6-5ccf.cryptographyis tightly coupled topyOpenSSLin this repo (requirements.inalready pins pyOpenSSL to track the cryptography pin), so moving cryptography to 49 has to move the two packages that cap it below 49. They go together as one coordinated set, all bumped to their current latest:cryptography46.0.7 -> 49.0.0 (fixes GHSA-537c-gmf6-5ccf)pyOpenSSL26.0.0 -> 26.3.0 (26.0.0 requirescryptography<47; 26.3.0 requirescryptography>=49)msal1.34.0 -> 1.37.0 (1.34.0 capscryptography<49; 1.37.0 allows<51)cryptography cannot be bumped on its own; pyOpenSSL and msal are forced compatibility bumps.
ISSUE TYPE
COMPONENT NAME
ASCENDER VERSION
ADDITIONAL INFORMATION
Found by
pip-auditagainstrequirements/requirements.txton current main. Validated in the dev container with the three new versions installed:pip checkreports no conflicts among cryptography / pyOpenSSL / msal (the only unrelated notice is a pre-existingtox/cachetoolsdev pin).django.setup()), andcryptography,OpenSSLandmsalimport.awx/main/tests/unit/utils/test_encryption.pypasses 11/11 (Fernet encrypt/decrypt is the main cryptography consumer).