Skip to content

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.5#8

Open
ashokrajar wants to merge 1 commit into
masterfrom
snyk-fix-f19c1f558fb3b158b63d0755fd3c2a08
Open

[Snyk] Security upgrade cryptography from 45.0.7 to 46.0.5#8
ashokrajar wants to merge 1 commit into
masterfrom
snyk-fix-f19c1f558fb3b158b63d0755fd3c2a08

Conversation

@ashokrajar

@ashokrajar ashokrajar commented Feb 17, 2026

Copy link
Copy Markdown
Owner

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.txt
⚠️ Warning
paramiko 2.0.9 requires cryptography, 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 that adds a security pin for cryptography; main risk is compatibility/runtime issues if this project expects an older cryptography version.

Overview
Adds an explicit cryptography>=46.0.5 entry in requirements.txt (not previously listed) to remediate a security vulnerability flagged by Snyk and ensure the transitive dependency is constrained to a safe version.

Written by Cursor Bugbot for commit 511bee5. 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-15263096
@sonarqubecloud

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment thread requirements.txt
mutagen==1.31
click==6.2
paramiko==2.0.9
cryptography>=46.0.5 # 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.

Cryptography 46 incompatible with project's Python 3.7 requirement

High Severity

The newly pinned cryptography>=46.0.5 requires Python 3.8+, but this project targets Python 3.7 (as declared in Pipfile). Installing this dependency on the project's target Python version will fail, breaking the build entirely.

Fix in Cursor Fix in Web

Comment thread requirements.txt
mutagen==1.31
click==6.2
paramiko==2.0.9
cryptography>=46.0.5 # 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.

Paramiko 2.0.9 incompatible with cryptography 46.x series

High Severity

paramiko==2.0.9 was never tested or updated for cryptography>=46.0.5. Paramiko only added compatibility with cryptography ≥43 in version 3.4.1. Using this old paramiko with such a new cryptography is very likely to cause runtime import errors or broken cryptographic operations.

Additional Locations (1)

Fix in Cursor Fix in Web

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