Skip to content

[Snyk] Security upgrade werkzeug from 0.9.4 to 3.1.5 #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kirbyk wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade werkzeug from 0.9.4 to 3.1.5 #325

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion solutions/2.2.4 Using Flask: Extending the Search Route/requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ Flask==0.10.1
GnuPGInterface==0.3.2
Jinja2==2.7.2
MarkupSafe==0.18
Werkzeug==0.9.4
Werkzeug==3.1.5

@cursor cursor Bot Jan 20, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Incompatible Werkzeug upgrade breaks Flask 0.10.1

High Severity

Upgrading Werkzeug from 0.9.4 to 3.1.5 while keeping Flask==0.10.1 causes a breaking incompatibility. Flask 0.10.1 (from 2013) relies on Werkzeug 0.x internal APIs that were removed or moved in Werkzeug 3.x. This will cause immediate import errors (e.g., cannot import name 'url_quote' from 'werkzeug.urls') and prevent the application from starting. Flask needs to be upgraded to at least version 2.x or 3.x to work with Werkzeug 3.1.5.

Fix in Cursor Fix in Web

apt-xapian-index==0.44
argparse==1.2.1
chardet==2.0.1
Expand Down