fix(anonymizer): bump cryptography to >=48.0.1,<49.0.0 to resolve GHSA-537c-gmf6-5ccf#2144
Open
SharonHart with Copilot wants to merge 2 commits into
Open
fix(anonymizer): bump cryptography to >=48.0.1,<49.0.0 to resolve GHSA-537c-gmf6-5ccf#2144SharonHart with Copilot wants to merge 2 commits into
SharonHart with Copilot wants to merge 2 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix cryptography vulnerability in presidio-anonymizer 2.2.363
fix(anonymizer): bump cryptography to >=48.0.1,<49.0.0 to resolve GHSA-537c-gmf6-5ccf
Jul 5, 2026
SharonHart
approved these changes
Jul 5, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates presidio-anonymizer’s cryptography dependency range to ensure installations can pick up the patched wheel version addressing GHSA-537c-gmf6-5ccf, improving security posture and compatibility with CVE-gated environments.
Changes:
- Bump
cryptographylower bound to>=48.0.1(patched) and set an upper cap of<49.0.0inpresidio-anonymizerpackaging metadata.
Contributor
Coverage report (presidio-cli)Click to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||
Contributor
Coverage report (presidio-anonymizer)Click to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||
Contributor
Contributor
Coverage report (presidio-image-redactor)Click to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||
Contributor
Coverage report (presidio-analyzer)Click to see where and how coverage changed
The report is truncated to 25 files out of 69. To see the full report, please visit the workflow summary page. This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
The
cryptography <47.0.0upper bound forced resolution to a range entirely below the patched version for GHSA-537c-gmf6-5ccf (HIGH — vulnerable OpenSSL statically linked into wheels, fixed only in 48.0.1), makingpresidio-anonymizerunadoptable in environments with CVE gates.Changes
presidio-anonymizer/pyproject.toml: Raise thecryptographyfloor to48.0.1and cap to<49.0.0The anonymizer uses only
cryptography.hazmat.primitives.ciphers(AES-CBC) andcryptography.hazmat.primitives.padding(PKCS7) — stable APIs with no breaking changes in 48.x.