Werkzeug safe_join not safe on Windows
Published 25 Oct 2024 · Updated 10 Sept 2026
Is your project on an affected werkzeug?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.0.6
- Fixed in
- 3.0.6
pip install 'werkzeug>=3.0.6'Details
On Python < 3.11 on Windows, os.path.isabs() does not catch UNC paths like //server/share. Werkzeug's safe_join() relies on this check, and so can produce a path that is not safe, potentially allowing unintended access to data. Applications using Python >= 3.11, or not using Windows, are not vulnerable.
Is GHSA-f9vj-2wh5-fj8j in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected werkzeug, and gives you the command that fixes it.
More advisories for werkzeug
- MediumCVE-2026-102598Werkzeug safe_join() allows Windows special device names · 5 Oct 2026
- MediumCVE-2026-27199 Werkzeug safe_join() allows Windows special device names · 19 Feb 2026
- MediumCVE-2026-21860 Werkzeug safe_join() allows Windows special device names with compound extensions · 8 Jan 2026
- MediumCVE-2025-66221Werkzeug safe_join() allows Windows special device names · 2 Dec 2025
- MediumCVE-2024-49767Werkzeug possible resource exhaustion when parsing file data in forms · 25 Oct 2024
- HighCVE-2024-34069Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain · 6 May 2024
References
- Linkgithub.com/pallets/werkzeug/security/advisories/GHSA-f9vj-2wh5-fj8j
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-49766
- Linkgithub.com/pallets/werkzeug/commit/2767bcb10a7dd1c297d812cc5e6d11a474c1f092
- Packagegithub.com/pallets/werkzeug
- Linkgithub.com/pallets/werkzeug/releases/tag/3.0.6
- Linksecurity.netapp.com/advisory/ntap-20250131-0005
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.