Search for packages
| purl | pkg:pypi/werkzeug@0.4 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-19qx-5d4g-pfdn
Aliases: CVE-2024-49766 GHSA-f9vj-2wh5-fj8j |
Werkzeug safe_join not safe on Windows 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. |
Affected by 3 other vulnerabilities. |
|
VCID-1qj3-zz1y-2ydy
Aliases: PYSEC-2019-70 |
Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id. |
Affected by 11 other vulnerabilities. |
|
VCID-3mxv-vxtj-8kde
Aliases: CVE-2026-21860 GHSA-87hc-h4r5-73f7 |
Werkzeug safe_join() allows Windows special device names with compound extensions 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 https://github.com/pallets/werkzeug/security/advisories/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. |
Affected by 1 other vulnerability. |
|
VCID-3t8t-yt9b-1fce
Aliases: CVE-2016-10516 GHSA-h2fp-xgx6-xh6f PYSEC-2017-43 |
Cross-site scripting (XSS) vulnerability in the render_full function in debug/tbtools.py in the debugger in Pallets Werkzeug before 0.11.11 (as used in Pallets Flask and other products) allows remote attackers to inject arbitrary web script or HTML via a field that contains an exception message. |
Affected by 13 other vulnerabilities. |
|
VCID-56e9-csba-kqa8
Aliases: CVE-2019-14806 GHSA-gq9m-qvpx-68hc PYSEC-2019-140 |
Pallets Werkzeug before 0.15.3, when used with Docker, has insufficient debugger PIN randomness because Docker containers share the same machine id. |
Affected by 11 other vulnerabilities. |
|
VCID-6cpm-rdw8-7fh6
Aliases: CVE-2025-66221 GHSA-hgf8-39gv-g3f2 |
Werkzeug safe_join() allows Windows special device names Werkzeug's `safe_join` function allows path segments with Windows device names. On Windows, there are special device names such as `CON`, `AUX`, etc that are implicitly present and readable in every directory. `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. |
Affected by 2 other vulnerabilities. |
|
VCID-bxfr-hpkh-cyby
Aliases: CVE-2023-46136 GHSA-hrfv-mqp8-q5rw PYSEC-2023-221 |
Werkzeug is a comprehensive WSGI web application library. If an upload of a file that starts with CR or LF and then is followed by megabytes of data without these characters: all of these bytes are appended chunk by chunk into internal bytearray and lookup for boundary is performed on growing buffer. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. This vulnerability has been patched in version 3.0.1. |
Affected by 6 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-fkmf-d4ju-bbc3
Aliases: CVE-2022-29361 PYSEC-2022-203 |
** DISPUTED ** Improper parsing of HTTP requests in Pallets Werkzeug v2.1.0 and below allows attackers to perform HTTP Request Smuggling using a crafted HTTP request with multiple requests included inside the body. NOTE: the vendor's position is that this behavior can only occur in unsupported configurations involving development mode and an HTTP server from outside the Werkzeug project. |
Affected by 9 other vulnerabilities. |
|
VCID-gv2s-q6ga-23gr
Aliases: CVE-2019-14322 GHSA-j544-7q9p-6xp8 |
Pallets Werkzeug vulnerable to Path Traversal In Pallets Werkzeug before 0.15.5, SharedDataMiddleware mishandles drive names (such as C:) in Windows pathnames. |
Affected by 10 other vulnerabilities. |
|
VCID-jxz2-8tqb-mbeg
Aliases: CVE-2026-27199 GHSA-29vq-49wr-vm6x |
Werkzeug safe_join() allows Windows special device names Werkzeug's `safe_join` function allows Windows device names as filenames if when preceded by other path segments. This was previously reported as https://github.com/pallets/werkzeug/security/advisories/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. |
Affected by 0 other vulnerabilities. |
|
VCID-kycs-rbvn-z3e7
Aliases: CVE-2023-23934 GHSA-px8h-6qxv-m22q PYSEC-2023-57 |
Werkzeug is a comprehensive WSGI web application library. Browsers may allow "nameless" cookies that look like `=value` instead of `key=value`. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key. The issue is fixed in Werkzeug 2.2.3. |
Affected by 7 other vulnerabilities. |
|
VCID-myg8-m4rh-ruae
Aliases: CVE-2024-49767 GHSA-q34m-jh98-gwm2 |
Werkzeug possible resource exhaustion when parsing file data in forms Applications using Werkzeug to parse `multipart/form-data` requests are vulnerable to resource exhaustion. A specially crafted form body can bypass the `Request.max_form_memory_size` setting. The `Request.max_content_length` setting, as well as resource limits provided by deployment software and platforms, are also available to limit the resources used during a request. This vulnerability does not affect those settings. All three types of limits should be considered and set appropriately when deploying an application. |
Affected by 3 other vulnerabilities. |
|
VCID-q13z-976n-gke3
Aliases: CVE-2020-28724 GHSA-3p3h-qghp-hvh2 PYSEC-2020-157 |
Open redirect vulnerability in werkzeug before 0.11.6 via a double slash in the URL. |
Affected by 14 other vulnerabilities. |
|
VCID-qjcy-54yn-qybs
Aliases: CVE-2024-34069 GHSA-2g68-c3qc-8985 |
Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain The debugger in affected versions of Werkzeug can allow an attacker to execute code on a developer's machine under some circumstances. This requires the attacker to get the developer to interact with a domain and subdomain they control, and enter the debugger PIN, but if they are successful it allows access to the debugger even if it is only running on localhost. This also requires the attacker to guess a URL in the developer's application that will trigger the debugger. |
Affected by 5 other vulnerabilities. |
|
VCID-qn4r-71h3-sbgb
Aliases: CVE-2023-25577 GHSA-xg9f-g7g7-2323 PYSEC-2023-58 |
Werkzeug is a comprehensive WSGI web application library. Prior to version 2.2.3, Werkzeug's multipart form data parser will parse an unlimited number of parts, including file parts. Parts can be a small amount of bytes, but each requires CPU time to parse and may use more memory as Python data. If a request can be made to an endpoint that accesses `request.data`, `request.form`, `request.files`, or `request.get_data(parse_form_data=False)`, it can cause unexpectedly high resource usage. This allows an attacker to cause a denial of service by sending crafted multipart data to an endpoint that will parse it. The amount of CPU time required can block worker processes from handling legitimate requests. The amount of RAM required can trigger an out of memory kill of the process. Unlimited file parts can use up memory and file handles. If many concurrent requests are sent continuously, this can exhaust or kill all available workers. Version 2.2.3 contains a patch for this issue. |
Affected by 7 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||