Skip to content

[SECURITY] Update dependency Werkzeug to v3.1.6#87

Open
specmatic-builder wants to merge 1 commit intomainfrom
renovate/pypi-werkzeug-vulnerability
Open

[SECURITY] Update dependency Werkzeug to v3.1.6#87
specmatic-builder wants to merge 1 commit intomainfrom
renovate/pypi-werkzeug-vulnerability

Conversation

@specmatic-builder
Copy link
Contributor

@specmatic-builder specmatic-builder commented Jan 9, 2026

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Werkzeug (changelog) >=3.1.4>=3.1.6 age adoption passing confidence
Werkzeug (changelog) ==3.1.4==3.1.6 age adoption passing confidence

Werkzeug safe_join() allows Windows special device names with compound extensions

CVE-2026-21860 / GHSA-87hc-h4r5-73f7

More information

Details

Werkzeug's safe_join function allows path segments with Windows device names that have file extensions or trailing spaces. On Windows, there are special device names such as CON, AUX, etc that are implicitly present and readable in every directory. Windows still accepts them with any file extension, such as CON.txt, or trailing spaces such as CON .

This was previously reported as GHSA-hgf8-39gv-g3f2, but the fix failed to account for compound extensions such as CON.txt.html or trailing spaces. It also missed some additional special names.

send_from_directory uses safe_join to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Werkzeug safe_join() allows Windows special device names

CVE-2026-27199 / GHSA-29vq-49wr-vm6x

More information

Details

Werkzeug's safe_join function allows Windows device names as filenames if when preceded by other path segments.

This was previously reported as GHSA-hgf8-39gv-g3f2, but the added filtering failed to account for the fact that safe_join accepts paths with multiple segments, such as example/NUL.

send_from_directory uses safe_join to safely serve files at user-specified paths under a directory. If the application is running on Windows, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

pallets/werkzeug (Werkzeug)

v3.1.6

Compare Source

Released 2026-02-19

  • safe_join on Windows does not allow special devices names in
    multi-segment paths. :ghsa:29vq-49wr-vm6x
  • Response.make_conditional sets the Accept-Ranges header even if it
    is not a satisfiable range request. :issue:3108

v3.1.5

Compare Source

Released 2026-01-08

  • safe_join on Windows does not allow more special device names, regardless
    of extension or surrounding spaces. :ghsa:87hc-h4r5-73f7
  • The multipart form parser handles a \r\n sequence at a chunk boundary.
    This fixes the previous attempt, which caused incorrect content lengths.
    :issue:3065 :issue:3077
  • Fix AttributeError when initializing DebuggedApplication with
    pin_security=False. :issue:3075

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. Specmatic specific configuration is managed here.

@specmatic-builder specmatic-builder force-pushed the renovate/pypi-werkzeug-vulnerability branch 2 times, most recently from acb0639 to 1b86e5f Compare January 13, 2026 18:12
@specmatic-builder specmatic-builder force-pushed the renovate/pypi-werkzeug-vulnerability branch from 1b86e5f to 2d4c84d Compare February 23, 2026 06:38
@specmatic-builder specmatic-builder changed the title [SECURITY] Update dependency Werkzeug to v3.1.5 [SECURITY] Update dependency Werkzeug to v3.1.6 Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant