Skip to content

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.6#65

Open
madisonmay wants to merge 1 commit intomasterfrom
snyk-fix-a60e869c70daa01411cefaa1ab03fdb4
Open

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.6#65
madisonmay wants to merge 1 commit intomasterfrom
snyk-fix-a60e869c70daa01411cefaa1ab03fdb4

Conversation

@madisonmay
Copy link
Copy Markdown

@madisonmay madisonmay commented Mar 29, 2026

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):

  • requirements/test.txt
⚠️ Warning
pytest-subtests 0.13.1 has requirement pytest>=7.0, but you have pytest 6.2.5.
moto 4.2.14 requires cryptography, which is not installed.
celery 5.3.0 requires kombu, which is not installed.

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


Note

Low Risk
Low risk dependency-only change limited to the test dependency set. Main risk is potential incompatibility in test tooling that indirectly relies on cryptography.

Overview
Pins cryptography>=46.0.6 in requirements/test.txt (even though it’s not a direct dependency) to address a reported vulnerability in the test dependency tree.

Written by Cursor Bugbot for commit beebeee. This will update automatically on new commits. Configure here.

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-CRYPTOGRAPHY-15809188
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: beebeee25d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

pre-commit
-r extras/yaml.txt
-r extras/msgpack.txt
cryptography>=46.0.6 # not directly required, pinned by Snyk to avoid a vulnerability
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Avoid forcing cryptography>=46 in Python 3.7 test envs

This new unconditional requirement applies to every tox environment that installs requirements/test.txt, including the Python 3.7 jobs still configured in tox.ini and .github/workflows/python-package.yml. cryptography 46.x no longer provides Python 3.7-compatible distributions, so this bound makes dependency resolution fail before tests run in those environments. The version floor should be guarded with a Python-version marker (or equivalent split constraint) so 3.7 jobs can still install dependencies.

Useful? React with 👍 / 👎.

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.

2 participants