How severe is GHSA-v2wj-q39q-566r?

No CVSS score has been assigned to GHSA-v2wj-q39q-566r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v2wj-q39q-566r?

GHSA-v2wj-q39q-566r affects the following packages: vite (npm), vite (npm). Ecosystems affected: npm.

How do I fix GHSA-v2wj-q39q-566r?

Update vite to 8.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2wj-q39q-566r is resolved across your whole dependency graph.

How do I detect GHSA-v2wj-q39q-566r 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-v2wj-q39q-566r 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-v2wj-q39q-566r?

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

Is GHSA-v2wj-q39q-566r actively exploited in the wild?

No public exploit code has been indexed for GHSA-v2wj-q39q-566r 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-v2wj-q39q-566r?

GHSA-v2wj-q39q-566r has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th 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-v2wj-q39q-566r?

GHSA-v2wj-q39q-566r is classified as CWE-180 (CWE-180), CWE-284 (CWE-284), CWE-472 (CWE-472). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-v2wj-q39q-566r?

A Nuclei detection template exists for GHSA-v2wj-q39q-566r, 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-v2wj-q39q-566r published, and has it been updated?

GHSA-v2wj-q39q-566r was published on April 6, 2026 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-v2wj-q39q-566r — vite

Fix: vitejs/vite#22160

GHSA-v2wj-q39q-566r is a CWE-180 vulnerability in vite. A fix is available for vite — see the affected versions and patch details below.

Vite: `server.fs.deny` bypassed with queries

Also known asCVE-2026-39364

Published

Apr 6, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 20, 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-v2wj-q39q-566r.

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

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

2 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

132.0Mdownloads / week

Description

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

explicitly exposes the Vite dev server to the network (using --host or server.host config option)
the sensitive file exists in the allowed directories specified by server.fs.allow
the sensitive file is denied with a pattern that matches a file by server.fs.deny

Details

On the Vite dev server, files that should be blocked by server.fs.deny (e.g., .env, *.crt) can be retrieved with HTTP 200 responses when query parameters such as ?raw, ?import&raw, or ?import&url&inline are appended.

PoC

Start the dev server: pnpm exec vite root --host 127.0.0.1 --port 5175 --strictPort
Confirm that server.fs.deny is enforced (expect 403): curl -i http://127.0.0.1:5175/src/.env | head -n 20 <img width="3944" height="1092" alt="image" src="https://github.com/user-attachments/assets/ecb9f2e0-e08f-4ac7-b194-e0f988c4cd4f" />
Confirm that the same files can be retrieved with query parameters (expect 200): <img width="2014" height="373" alt="image" src="https://github.com/user-attachments/assets/76bc2a6a-44f4-4161-ae47-eab5ae0c04a8" />

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vite`	≥ 8.0.0&&< 8.0.5	8.0.5`npm install vite@8.0.5`
📦npm	`vite`	≥ 7.1.0&&< 7.3.2	7.3.2`npm install vite@7.3.2`

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 8.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2wj-q39q-566r 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-v2wj-q39q-566r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-v2wj-q39q-566r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect GHSA-v2wj-q39q-566r

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

nuclei -id ghsa-v2wj-q39q-566r -u https://target

Template: Vite Dev Server - Directory Traversal
Severity: high
Impact: Attackers can retrieve sensitive files like .env or certificates, leading to information disclosure.
Remediation: Update to versions 7.3.2 or 8.0.5 or later.

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

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 HatImportant

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-tech-preview/mcp-server-rhel9:1779783248`	RHSA-2026:24866

Frequently Asked Questions

### Summary The contents of files that are specified by [`server.fs.deny`](https://vite.dev/config/server-options#server-fs-deny) can be returned to the browser. ### Impact Only apps that match the following conditions are affected: - explicitly exposes the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) - the sensitive file exists in the allowed directories specified by [`server.fs.allow`](https://vite.dev/config/server-options#server-fs-allow) - the sensitive file is denied with a pattern that mat

O3 Security · Impact-Aware SCA

Is GHSA-v2wj-q39q-566r in your dependencies?

O3 Security finds GHSA-v2wj-q39q-566r 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