Skip to content

[Snyk] Security upgrade cryptography from 45.0.7 to 48.0.1#50

Open
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-004e5b145a3a1b85b964bc219b3408f7
Open

[Snyk] Security upgrade cryptography from 45.0.7 to 48.0.1#50
snyk-io[bot] wants to merge 1 commit into
masterfrom
snyk-fix-004e5b145a3a1b85b964bc219b3408f7

Conversation

@snyk-io

@snyk-io snyk-io Bot commented Jun 18, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • py3_test_requirements.txt
⚠️ Warning
moto 3.1.19 requires cryptography, which is not installed.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Out-of-bounds Read

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-17344551
@snyk-io

snyk-io Bot commented Jun 18, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

This major version upgrade from cryptography 45.x to 48.x introduces significant breaking changes, including dropped support for older Python and OpenSSL versions, and API modifications that require code changes.

Key Breaking Changes:

  • Python Version Requirement: Support for Python 3.7 was removed in v46.0.0, and support for Python 3.8 was removed in v48.0.0. The new minimum required version is Python 3.9. [2, 4]
  • OpenSSL Requirement: Support for OpenSSL versions older than 3.0.0 has been removed as of v47.0.0. Your build and runtime environment must use OpenSSL 3.0.0 or newer. [2, 8]
  • Exception Type Change: Loading keys with unsupported algorithms now raises UnsupportedAlgorithm instead of ValueError (since v47.0.0). Error handling code that catches ValueError during key loading must be updated to also catch UnsupportedAlgorithm. [4, 8]
  • Algorithm Removals:
    • Support for binary elliptic curves (SECT* classes) was removed in v47.0.0. [2]
    • The insecure ciphers TripleDES and ARC4 were removed from the main cipher module in v48.0.0. [2, 11]

Recommendation:
Before merging, verify that your environment meets the new Python (3.9+) and OpenSSL (3.0.0+) requirements. Audit your code to ensure you are not using the removed algorithms (TripleDES, ARC4, binary elliptic curves) and update any exception handling for key loading to catch UnsupportedAlgorithm.

Source: Cryptography Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@snyk-io

snyk-io Bot commented Jun 18, 2026

Copy link
Copy Markdown
Author

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants