deps-dev: bump werkzeug from 3.1.8 to 3.1.9

[dependabot]

Bumps werkzeug from 3.1.8 to 3.1.9.

Release notes

Sourced from werkzeug's releases.

3.1.9

This is the Werkzeug 3.1.9 security fix release, which fixes security issues and bugs but does not otherwise change behavior and should not result in breaking changes compared to the latest feature release.

PyPI: https://pypi.org/project/Werkzeug/3.1.9/ Changes: https://werkzeug.palletsprojects.com/page/changes/#version-3-1-9 Milestone: https://github.com/pallets/werkzeug/milestone/46?closed=1

• safe_join on Windows does not allow special devices names with empty ADS markers on NTFS. GHSA-g6x2-hccm-hh4m
• ProfilerMiddleware uses profiling.tracing on Python 3.15. #3207
• uri_to_iri and iri_to_uri preserve empty username, password, and port 0. #3189
• Improve performance of parse_options_header. #3231
• Improve performance of parse_etags. #3231
• Improve performance of parse_cookie. #3231
• get_host also checks that the port is in the valid range. #3236
• The int URL converter returns a 404 instead of 500 error when the value is longer than sys.get_int_max_str_digits(). #3237
• Improve debugger PIN generation from cgroup data inside Podman. #3245
• Authorization parsing basic auth disallows non-base64 characters. #3248
• application/x-www-form-urlencoded form data is no longer limited to max_form_memory_size, only max_content_length. #3251
• LimitedStream.readinto does not resize the buffer when it reads less than the remaining size. #3253
• Rules with 10 or more converters in a single part assign matched values correctly. #3254
• The invalid Range suffix length -0 is no longer accepted. #3255

Changelog

Sourced from werkzeug's changelog.

Version 3.1.9

Released 2026-09-27

• safe_join on Windows does not allow special devices names with empty ADS markers on NTFS. :ghsa:g6x2-hccm-hh4m
• ProfilerMiddleware uses profiling.tracing on Python 3.15. :issue:3207
• uri_to_iri and iri_to_uri preserve empty username, password, and port 0. :issue:3189
• Improve performance of parse_options_header. :pr:3231
• Improve performance of parse_etags. :pr:3231
• Improve performance of parse_cookie. :pr:3231
• get_host also checks that the port is in the valid range. :pr:3236
• The int URL converter returns a 404 instead of 500 error when the value is longer than sys.get_int_max_str_digits(). :issue:3237
• Improve debugger PIN generation from cgroup data inside Podman. :issue:3245
• Authorization parsing basic auth disallows non-base64 characters. :pr:3248
• application/x-www-form-urlencoded form data is no longer limited to max_form_memory_size, only max_content_length. :pr:3251
• LimitedStream.readinto does not resize the buffer when it reads less than the remaining size. :pr:3253
• Rules with 10 or more converters in a single part assign matched values correctly. :pr:3254
• The invalid Range suffix length -0 is no longer accepted. :pr:3255

Commits

• 6604c3b release version 3.1.9
• a78b30a update dependencies
• 8d77320 disallow special name with ads (#3309)
• b2a2c09 disallow special name with ads
• 4efac9d add links
• 400c23e Allow flit_core 4.x (#3261)
• 7132a19 allow flit_core 4
• 6fba87c only accept ASCII digits
• 263f5ca disallow range -0 (#3255)
• 0c419f9 disallow range -0
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

Dependency Security Audit

Scanned: pyproject.toml dependencies + dev group, resolved at Python 3.10 (the current resolution, and the lowest versions the published specs permit under each pydantic major)

⚠️ Advisories found, but none at HIGH or CRITICAL. This does not block the build.

Severity	Count
🔶 MEDIUM	1
❔ UNKNOWN	1

Severity	Package	Installed	Fixed in	Advisory
🔶 MEDIUM	uv	0.12.17	0.12.18	CVE-2026-104843
❔ UNKNOWN	uv	0.12.17	0.12.18	CVE-2026-104843 (GHSA-2cv4-cqwr-gwf7)

Advisory details

MEDIUM -- CVE-2026-104843 (uv 0.12.17)

Found by: trivy:dev-ceiling

uv: uv: Arbitrary code execution via malicious package extraction on Windows

UNKNOWN -- CVE-2026-104843 (GHSA-2cv4-cqwr-gwf7) (uv 0.12.17)

Found by: pip-audit:dev-ceiling

### Impact In versions of uv from 0.12.7 to 0.12.18 on Windows, uv could be induced into writing a file outside of the installation prefix during wheel installation. A malicious wheel could use this to place an executable outside of the intended environment, including in a directory already present on the user's PATH. This vulnerability only affects Windows hosts; no other platforms are affected. ### Patches uv 0.12.18 and newer address this vulnerability. Users are encouraged to upgrade to 0.12.18. ### Workarounds There is no workaround other than upgrading to uv 0.12.18.

How to fix

Raise the affected lower bound in pyproject.toml ([project].dependencies, or the pin in the dev dependency group) to at least the Fixed in version above, then run uv lock. Because this package publishes open >= ranges, the floor is what consumers can actually install -- bumping only the resolved version does not close the hole.

This audit resolves without the 7-day publish-age cooldown (exclude-newer) in [tool.uv], but uv lock applies it. If uv lock says the fixed version was filtered by exclude-newer, add exclude-newer-package = { <package> = false } under [tool.uv] in pyproject.toml, run uv lock and commit both files. Once the release is 7 days old, remove the entry and run uv lock again.

An advisory with no fix available does not block the build -- it is reported here so it can be tracked, but no version bump can resolve it. Suppression files are deliberately not honoured: the scan runs with --ignorefile /dev/null so nothing can disappear from this report silently.