Skip to content

[Snyk] Security upgrade werkzeug from 1.0.1 to 3.1.5 #35

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
ashmuck wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade werkzeug from 1.0.1 to 3.1.5 #35

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 requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,5 +38,5 @@ tqdm==4.57.0
typing-extensions==3.7.4.3
tzlocal==2.1
urllib3==1.26.3
Werkzeug==1.0.1
Werkzeug==3.1.5
Copy link
Copy Markdown

@cursor cursor Bot Jan 9, 2026

Choose a reason for hiding this comment

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

Werkzeug 3.x incompatible with tensorboard 2.4.1

Medium Severity

Upgrading Werkzeug from 1.0.1 to 3.1.5 introduces a dependency incompatibility with tensorboard==2.4.1. TensorBoard 2.4.1 (from early 2021) uses internal werkzeug APIs that were removed in werkzeug 2.x/3.x, causing ImportError exceptions (e.g., cannot import name '_plain_int' from 'werkzeug._internal') when running the TensorBoard web server. The codebase uses SummaryWriter for logging training metrics, and while log writing may still work, users attempting to view metrics via tensorboard command will encounter runtime failures. Either tensorboard needs to be upgraded alongside werkzeug, or werkzeug's version constraint needs adjustment.

Fix in Cursor Fix in Web

zipp==3.4.0
Loading