Skip to content

[Snyk] Fix for 2 vulnerabilities#49

Open
danielberman79 wants to merge 1 commit into
masterfrom
snyk-fix-f9d8b7dc5c58eb64b3abefa771d2d75c
Open

[Snyk] Fix for 2 vulnerabilities#49
danielberman79 wants to merge 1 commit into
masterfrom
snyk-fix-f9d8b7dc5c58eb64b3abefa771d2d75c

Conversation

@danielberman79
Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt

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:

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

@danielberman79
Copy link
Copy Markdown
Owner Author

Merge Risk: High

This upgrade involves major version jumps for both Flask (1.1.1 → 3.1.3) and its core dependency Werkzeug (1.0.0 → 3.1.6), introducing significant breaking changes that require developer action.

Key Breaking Changes:

  • Python Version Requirement: Support for Python versions 2.7, 3.5, 3.6, and 3.7 has been dropped. Your application must be running on Python 3.8 or newer. [5, 7, 10]
  • Werkzeug Security Hashing: In Werkzeug 3.0, generate_password_hash now uses scrypt by default instead of pbkdf2:sha256. If your application uses Werkzeug for password management, existing password hashes will fail validation. [5, 7]
  • Removal of Deprecated APIs: Functions and parameters deprecated in previous versions have been removed. This includes:
    • Flask's Config.from_json() is removed. Use Config.from_file() instead. [2, 8, 10]
    • Flask's safe_join is removed. Use werkzeug.utils.safe_join instead. [8, 10]
    • Renamed send_file parameters (e.g., attachment_filename is now download_name). [2]
  • Dependency Requirements: Flask 3.0 requires Werkzeug 3.0, meaning these upgrades must be handled together. [3, 10]

Recommendation:

  1. Verify Python Version: Ensure your production environment and deployment pipeline use Python 3.8 or higher.
  2. Address Password Hashing: If using werkzeug.security for passwords, you must implement a strategy to handle the new hashing default. This may involve re-hashing user passwords or explicitly setting the hashing method to the legacy algorithm during a transition.
  3. Update Deprecated Code: Review your codebase for use of removed functions like Config.from_json and update them to their modern equivalents.
  4. Thorough Testing: Due to the extensive nature of these changes, a full testing cycle is essential to catch issues related to API removals and behavioral changes.

Source: Flask Changes, Werkzeug Changes

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

@danielberman79
Copy link
Copy Markdown
Owner Author

danielberman79 commented Feb 21, 2026

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

Status Scanner 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.

2 participants