{"answers":{"affected":"3 open source packages ship an affected version, including werkzeug and Werkzeug.","exploited":"There is no known exploitation of CVE-2026-102598 in the wild and no public exploit code.","fix":"Upgrade werkzeug to 3.1.9 or later.","what":"CVE-2026-102598 is a medium-severity denial of service vulnerability in pallets werkzeug, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102598 and fix it if it is affected.\n\nWhat it is: CVE-2026-102598 is a medium-severity denial of service vulnerability in pallets werkzeug, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102598 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- werkzeug (PyPI): affected all versions; fixed in 3.1.9\n- werkzeug (PyPI): affected all versions; fixed in 3.1.9\n- Werkzeug (PyPI): affected all versions; fixed in 3.1.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102598/ (Markdown: https://insights.sbomify.com/CVE-2026-102598/index.md)","id":"CVE-2026-102598","markdown":"https://insights.sbomify.com/CVE-2026-102598/index.md","name":"CVE-2026-102598","record":{"aliases":["AZL-105654","AZL-105681","AZL-105921","CLEANSTART-2026-IZ97021","CLEANSTART-2026-JH53704","CLSA-2026-1791363861","CLSA-2026-1791366853","ECHO-f310-f2a8-f5e5","GHSA-g6x2-hccm-hh4m","MINI-4fx4-r97c-6pp3","MINI-672p-xpxm-7626","MINI-6p6r-7vmq-7hmh","MINI-92h9-r9m3-c7vm","MINI-fxv8-grph-v6m6","MINI-hpvp-vg36-rxvg","MINI-jmp8-qw7p-99gx","MINI-pgf6-2v95-5v3q","MINI-w2xm-mc39-8jwp","MINI-x853-7prg-g8pv","PYSEC-2026-4312","UBUNTU-CVE-2026-102598"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Python web library","requires_auth":"none","summary":"An attacker can cause indefinite hangs in applications using Werkzeug on Windows by requesting paths with special device names and empty ADS markers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-67","name":"Improper Handling of Windows Device Names"}],"description":"Werkzeug is a comprehensive WSGI web application library. Prior to 3.1.9, the safe_join function used by send_from_directory can allow a NUL: special-device path because safe_join checks the Windows device name without first removing an empty NTFS ADS marker. The trigger is that an application runs on Windows with NTFS and serves a user-specified path ending in a special device name such as NUL:. The attack mechanism is that a requested path ends in a Windows special device name with an empty ADS marker. The impact is that the special device opens successfully and the file read hangs indefinitely. This issue is fixed in version 3.1.9.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Werkzeug safe_join() allows Windows special device names","id":"CVE-2026-102598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Socket.IO: Engine.IO Protocol Revision Mismatch DoS","id":"CVE-2026-102599"},"packages":[{"ecosystem":"PyPI","fixed":["3.1.9"],"introduced":["0"],"last_affected":[],"package":"Werkzeug","purl":null,"source":"GHSA-g6x2-hccm-hh4m"},{"ecosystem":"PyPI","fixed":["3.1.9"],"introduced":["0"],"last_affected":[],"package":"werkzeug","purl":"pkg:pypi/werkzeug","source":"GHSA-g6x2-hccm-hh4m"},{"ecosystem":"PyPI","fixed":["3.1.9"],"introduced":["0"],"last_affected":[],"package":"werkzeug","purl":"pkg:pypi/werkzeug","source":"PYSEC-2026-4312"}],"prev":{"headline":"Nango: Production flow RBAC bypass on private flow-read routes","id":"CVE-2026-102596"},"products":["werkzeug"],"published":"2026-09-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["pallets"]},"summary":"An attacker can cause indefinite hangs in applications using Werkzeug on Windows by requesting paths with special device names and empty ADS markers.","url":"https://insights.sbomify.com/CVE-2026-102598/"}