How severe is GHSA-g6x2-hccm-hh4m?

No CVSS score has been assigned to GHSA-g6x2-hccm-hh4m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g6x2-hccm-hh4m?

GHSA-g6x2-hccm-hh4m affects the following packages: werkzeug (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-g6x2-hccm-hh4m?

Update werkzeug to 3.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6x2-hccm-hh4m is resolved across your whole dependency graph.

How do I detect GHSA-g6x2-hccm-hh4m in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for werkzeug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g6x2-hccm-hh4m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g6x2-hccm-hh4m actively exploited in the wild?

No public exploit code has been indexed for GHSA-g6x2-hccm-hh4m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-g6x2-hccm-hh4m?

GHSA-g6x2-hccm-hh4m has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g6x2-hccm-hh4m?

GHSA-g6x2-hccm-hh4m is classified as CWE-67 (CWE-67). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g6x2-hccm-hh4m published, and has it been updated?

GHSA-g6x2-hccm-hh4m was published on October 5, 2026 and was last updated on October 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Werkzeug safe_join() allows Windows special device namesGHSA-g6x2-hccm-hh4m

Fix: pallets/werkzeug#3309

GHSA-g6x2-hccm-hh4m is a CWE-67 vulnerability in werkzeug. A fix is available for werkzeug — see the affected versions and patch details below.

Also known asCVE-2026-102598PYSEC-2026-4312

Published

Oct 5, 2026

Updated

Oct 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g6x2-hccm-hh4m.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍werkzeug

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Werkzeug's safe_join function allows Windows device names as filenames when they have an empty ADS marker on NTFS.

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 Windows allows special device names with an empty ADS marker, such as 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 NTFS, and the requested path ends with a special device name, the file will be opened successfully, but reading will hang indefinitely.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`werkzeug`	all versions	3.1.9`pip install --upgrade 'werkzeug==3.1.9'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for werkzeug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update werkzeug to 3.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6x2-hccm-hh4m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat AI Inference Server 3.4	`rhaii/vllm-cpu-rhel9:1791857301`	RHSA-2026:83112
Red Hat AI Inference Server 3.4	`rhaii/vllm-cuda-rhel9:1791857183`	RHSA-2026:83120
Red Hat AI Inference Server 3.5	`rhaii/vllm-gaudi-rhel9:1791427182`	RHSA-2026:82061
Red Hat AI Inference Server 3.5	`rhaii/vllm-cuda-rhel9:1791473631`	RHSA-2026:82368
Red Hat AI Inference Server 3.5	`rhaii/vllm-cpu-rhel9:1791473614`	RHSA-2026:82415

Frequently Asked Questions

Werkzeug's `safe_join` function allows Windows device names as filenames when they have an empty ADS marker on NTFS. 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 Windows allows special device names with an empty ADS marker, such as `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 NTFS, and the requested path ends with a special device name, the file will be opened succ

O3 Security · Impact-Aware SCA

Is GHSA-g6x2-hccm-hh4m in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works