How severe is GHSA-f9vj-2wh5-fj8j?

No CVSS score has been assigned to GHSA-f9vj-2wh5-fj8j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f9vj-2wh5-fj8j?

GHSA-f9vj-2wh5-fj8j affects the following packages: werkzeug (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-f9vj-2wh5-fj8j?

Update werkzeug to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9vj-2wh5-fj8j is resolved across your whole dependency graph.

How do I detect GHSA-f9vj-2wh5-fj8j 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-f9vj-2wh5-fj8j if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How does O3 Security protect against GHSA-f9vj-2wh5-fj8j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f9vj-2wh5-fj8j can be triaged on real exposure rather than presence alone.

Is GHSA-f9vj-2wh5-fj8j actively exploited in the wild?

No public exploit code has been indexed for GHSA-f9vj-2wh5-fj8j 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-f9vj-2wh5-fj8j?

GHSA-f9vj-2wh5-fj8j has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 54th 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-f9vj-2wh5-fj8j?

GHSA-f9vj-2wh5-fj8j is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-f9vj-2wh5-fj8j published, and has it been updated?

GHSA-f9vj-2wh5-fj8j was published on October 25, 2024 and was last updated on September 10, 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

GHSA-f9vj-2wh5-fj8j — werkzeug

Fix: pallets/werkzeug@2767bcb

GHSA-f9vj-2wh5-fj8j is a Path Traversal vulnerability in werkzeug. A fix is available for werkzeug — see the affected versions and patch details below.

Werkzeug safe_join not safe on Windows

Also known asCVE-2024-49766PYSEC-2026-2045

Published

Oct 25, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-f9vj-2wh5-fj8j.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 is a Web Server Gateway Interface web application library. 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. Werkzeug version 3.0.6 contains a patch.

Affected Packages

1 total 1 fixed

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

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.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f9vj-2wh5-fj8j is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f9vj-2wh5-fj8j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f9vj-2wh5-fj8j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-f9vj-2wh5-fj8j in your dependencies?

O3 Security finds GHSA-f9vj-2wh5-fj8j across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works