NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2022-35204 — vite

HIGHFix: vitejs/vite@6851009

CVE-2022-35204 is a high-severity (CVSS 8.6) Path Traversal vulnerability in vite. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for vite — see the affected versions and patch details below.

Vite before v2.9.13 vulnerable to directory traversal via crafted URL to victim's service

Also known asGHSA-mv48-hcvh-8jj8
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk+0.04%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk
0.47%0.92%1.38%1.83%1.0%1.3%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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
262.8Mdownloads / week

Description

Vitejs Vite before v2.9.13 was discovered to allow attackers to perform a directory traversal via a crafted URL to the victim's service.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmviteall versions2.9.13npm install vite@2.9.13
📦npmvite≥ 3.0.0-alpha.0&&< 3.0.0-beta.43.0.0-beta.4npm install vite@3.0.0-beta.4

Affected Products

1 product · 1 configurations
Application
vitevitejs
< 2.9.13
range
Exploits & PoCs
1

Research 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 dependency
  1. 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.

  2. Fix

    Update vite to 2.9.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35204 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

Vitejs Vite before v2.9.13 was discovered to allow attackers to perform a directory traversal via a crafted URL to the victim's service.
O3 Security · Impact-Aware SCA

Is CVE-2022-35204 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-35204: vite Path Traversal — Fixed in 2.9.13