Vite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryGHSA-4r4m-qw57-chr8
MEDIUMFix: vitejs/vite@5967313GHSA-4r4m-qw57-chr8 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in vite. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-01-22) — treat it as actively exploited and patch now. A fix is available for vite — see the affected versions and patch details below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-01-22. Federal agencies were required to remediate by 2026-02-12.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-4r4m-qw57-chr8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-4r4m-qw57-chr8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
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.
vitenpmDescription
Summary
The contents of arbitrary files 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.
Details
- base64 encoded content of non-allowed files is exposed using
?inline&import(originally reported as?import&?inline=1.wasm?init) - content of non-allowed files is exposed using
?raw?import
/@fs/ isn't needed to reproduce the issue for files inside the project root.
PoC
Original report (check details above for simplified cases):
The ?import&?inline=1.wasm?init ending allows attackers to read arbitrary files and returns the file content if it exists. Base64 decoding needs to be performed twice
$ npm create vite@latest
$ cd vite-project/
$ npm install
$ npm run dev
Example full URL http://localhost:5173/@fs/C:/windows/win.ini?import&?inline=1.wasm?init
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | vite | ≥ 6.2.0&&< 6.2.4 | 6.2.4npm install vite@6.2.4 |
| 📦npm | vite | ≥ 6.1.0&&< 6.1.3 | 6.1.3npm install vite@6.1.3 |
| 📦npm | vite | ≥ 6.0.0&&< 6.0.13 | 6.0.13npm install vite@6.0.13 |
| 📦npm | vite | ≥ 5.0.0&&< 5.4.16 | 5.4.16npm install vite@5.4.16 |
| 📦npm | vite | all versions | 4.5.11npm install vite@4.5.11 |
Affected Products
vitevitejsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r4m-qw57-chr8 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
How to detect GHSA-4r4m-qw57-chr8
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-4r4m-qw57-chr8 -u https://target- Template
- Vite Development Server - Path Traversal
- Severity
- medium
- Impact
- Attackers can exploit path traversal in the @fs endpoint to access files outside the intended directory when the Vite dev server is exposed to the network, potentially reading sensitive system files.
- Remediation
- Upgrade to the patched version or avoid exposing the Vite development server to the network (do not use --host flag or configure server.host); if upgrading is not immediately possible, implement access restrictions to the Vite development server
Template by ProjectDiscovery nuclei-templates (martian, ritikchaddha, v2htw), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-4r4m-qw57-chr8 in your dependencies?
Find it across npm, including transitive dependencies.