How severe is GHSA-859w-5945-r5v3?

No CVSS score has been assigned to GHSA-859w-5945-r5v3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-859w-5945-r5v3?

GHSA-859w-5945-r5v3 affects the following packages: vite (npm), vite (npm), vite (npm), vite (npm), vite (npm). Ecosystems affected: npm.

How do I fix GHSA-859w-5945-r5v3?

Update vite to 6.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-859w-5945-r5v3 is resolved across your whole dependency graph.

How do I detect GHSA-859w-5945-r5v3 in my npm dependencies?

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

How do I mitigate GHSA-859w-5945-r5v3 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.

How does O3 Security protect against GHSA-859w-5945-r5v3?

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

Is GHSA-859w-5945-r5v3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-859w-5945-r5v3 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-859w-5945-r5v3?

GHSA-859w-5945-r5v3 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 66th 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-859w-5945-r5v3?

GHSA-859w-5945-r5v3 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.

Is there exploit tooling available for GHSA-859w-5945-r5v3?

A Nuclei detection template exists for GHSA-859w-5945-r5v3, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-859w-5945-r5v3 published, and has it been updated?

GHSA-859w-5945-r5v3 was published on April 30, 2025 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.

📦 npm

Not in CISA KEV

GHSA-859w-5945-r5v3 — vite

Fix: vitejs/vite@c22c43d

GHSA-859w-5945-r5v3 is a Path Traversal vulnerability in vite. A fix is available for vite — see the affected versions and patch details below.

Vite's server.fs.deny bypassed with /. for files under project root

Also known asCVE-2025-46565

Published

Apr 30, 2025

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-859w-5945-r5v3.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% 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

5 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

vitenpm

131.1Mdownloads / week

Description

Summary

The contents of files in the project root that are denied by a file matching pattern can be returned to the browser.

Impact

Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected. Only files that are under project root and are denied by a file matching pattern can be bypassed.

Examples of file matching patterns: .env, .env.*, *.{crt,pem}, **/.env
Examples of other patterns: **/.git/**, .git/**, .git/**/*

Details

server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns). These patterns were able to bypass for files under root by using a combination of slash and dot (/.).

PoC

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env/. http://localhost:5173

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vite`	≥ 6.3.0&&< 6.3.4	6.3.4`npm install vite@6.3.4`
📦npm	`vite`	≥ 6.2.0&&< 6.2.7	6.2.7`npm install vite@6.2.7`
📦npm	`vite`	≥ 6.0.0&&< 6.1.6	6.1.6`npm install vite@6.1.6`
📦npm	`vite`	≥ 5.0.0&&< 5.4.19	5.4.19`npm install vite@5.4.19`
📦npm	`vite`	all versions	4.5.14`npm install vite@4.5.14`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vite to 6.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-859w-5945-r5v3 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-859w-5945-r5v3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-859w-5945-r5v3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-859w-5945-r5v3

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-859w-5945-r5v3 -u https://target

Template: Vite Dev Server - Information Exposure
Severity: medium

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Summary The contents of files in [the project `root`](https://vite.dev/config/shared-options.html#root) that are denied by a file matching pattern can be returned to the browser. ### Impact Only apps explicitly exposing the Vite dev server to the network (using --host or [server.host config option](https://vitejs.dev/config/server-options.html#server-host)) are affected. Only files that are under [project `root`](https://vite.dev/config/shared-options.html#root) and are denied by a file matching pattern can be bypassed. - Examples of file matching patterns: `.env`, `.env.*`, `*.{crt,pem

O3 Security · Impact-Aware SCA

Is GHSA-859w-5945-r5v3 in your dependencies?

O3 Security finds GHSA-859w-5945-r5v3 across npm 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