Skip to content

fix: bump werkzeug to 3.1.9 for PYSEC-2026-4312 - #394

Merged
luis5tb merged 1 commit into
RHEcosystemAppEng:mainfrom
luis5tb:werkzeug-cve
Oct 28, 2026
Merged

luis5tb merged 1 commit into
RHEcosystemAppEng:mainfrom
luis5tb:werkzeug-cve

Conversation

@luis5tb

@luis5tb luis5tb commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

Bumps the werkzeug pin in the eval environment from 3.1.8 to 3.1.9, the first fixed version for PYSEC-2026-4312. Werkzeug is a transitive dependency here (via flask/flask-cors in the MLflow eval tooling) and is not present in the agent or dev environments. Verified with pip-audit --require-hashes.

The werkzeug>=3.1.9 floor is now also pinned in the eval extra of pyproject.toml, following the repo convention for transitive dependency CVE pins, so the constraint is enforced on lock file regeneration and not only in the lock file itself.

@luis5tb
luis5tb force-pushed the werkzeug-cve branch 3 times, most recently from 3fb66e9 to 1d28635 Compare October 28, 2026 12:13
Bumps the werkzeug pin in the eval environment from 3.1.8 to
3.1.9, the first fixed version for PYSEC-2026-4312. Werkzeug is
a transitive dependency here (via flask/flask-cors in the
MLflow eval tooling) and is not present in the agent or dev
environments. Verified with pip-audit --require-hashes.

The werkzeug>=3.1.9 floor is now also pinned in the eval extra
of pyproject.toml, following the repo convention for transitive
dependency CVE pins, so the constraint is enforced on lock file
regeneration and not only in the lock file itself.
@luis5tb
luis5tb merged commit d67eeeb into RHEcosystemAppEng:main Oct 28, 2026
9 of 15 checks passed
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