Answer in brief
CVE-2023-34092 records a High severity (CVSS 7.5) vulnerability in Vite Server Options (server.fs.deny) can be bypassed using double forward-slash (//). The current sources do not mark it as known exploited. The current feed maps vite (npm), vite (npm), vite (npm), vite (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vite (npm), vite (npm), vite (npm), vite (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vitenpm | 2.9.15 | Not reported |
| vitenpm | >=3.0.2<=3.2.6 | Not reported |
| vitenpm | >=4.0.0<=4.0.4 | Not reported |
| vitenpm | >=4.1.0<=4.1.4 | Not reported |
| vitenpm | >=4.2.0<=4.2.2 | Not reported |
| vitenpm | >=4.3.0<=4.3.8 | Not reported |
| vitenpm | >=0 <2.9.16 | 2.9.16 |
| vitenpm | >=3.0.2 <3.2.7 | 3.2.7 |
| vitenpm | >=4.0.0 <4.0.5 | 4.0.5 |
| vitenpm | >=4.1.0 <4.1.5 | 4.1.5 |
| vitenpm | >=4.2.0 <4.2.3 | 4.2.3 |
| vitenpm | >=4.3.0 <4.3.9 | 4.3.9 |
Published upstream
Jun 1, 2023
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Aug 25, 2026
The issue involves a security vulnerability in Vite where the server options can be bypassed using a double forward slash (`//`). This vulnerability poses a potential security risk as it can allow unauthorized access to sensitive directories and files. ### Steps to Fix. **Update Vite**: Ensure that you are using the latest version of Vite. Security issues like this are often fixed in newer releases.\n2. **Secure the server configuration**: In your `vite.config.js` file, review and update the server configuration options to restrict access to unauthorized requests or directories. ### Impact Only users explicitly exposing the Vite dev server to the network (using `--host` or the [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) are affected and only files in the immediate Vite project root folder could be exposed.\n\n### Patches\nFixed in vite@**4.3.9**, vite@**4.2.3**, vite@**4.1.5**, vite@**4.0.5** and in the latest minors of the previous two majors, vite@**3.2.7** and vite@**2.9.16**. ### Details Vite serves the application with under the root-path of the project while running on the dev mode. By default, Vite uses the server option fs.deny to protect sensitive files. But using a simple double forward-slash, we can bypass this restriction. \n\n### PoC\n1. Create a new latest project of Vite using any package manager. (here I'm using react and vue templates and pnpm for testing)\n2. Serve the application on dev mode using `pnpm run dev`.\n3. Directly access the file via url using double forward-slash (`//`) (e.g: `//.env`, `//.env.local`)\n4. The server option `fs.deny` was successfully bypassed. Proof Images: \n
Quoted source text, attributed separately from HOL analysis.