# CVE-2026-112946: Vite: Files outside `server.fs.allow` could be served when project paths match system paths on non-Windows machine


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** CLSA-2026-1793098696, ECHO-8b2a-34a4-579e, GHSA-rq7h-c2jc-7f22, UBUNTU-CVE-2026-112946

## What is CVE-2026-112946?

CVE-2026-112946 is a medium-severity vulnerability in vitejs vite, published on 20 Oct 2026. 

### Official description

Vite is a frontend tooling framework for JavaScript. Prior to 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3, import analysis can record a root-relative browser URL in safeModulePaths instead of the cleaned resolved module identifier. On a network-accessible, non-Windows development server, an imported project file whose URL matches an absolute host path can authorize a later raw-filesystem request for that host file, provided server.fs.deny does not block it. The request can disclose the matching file outside the project root, but it does not allow arbitrary path traversal because the host path must correspond to a project-relative URL authorized by the application graph. This issue is fixed in versions 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3.

Weakness: CWE-284 (Improper Access Control), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-112946?

12 open source packages ship an affected version, including vite and vite-plus.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vite` | npm | All versions | 6.4.4 |
| `vite` | npm | All versions | 6.4.4 |
| `vite` | npm | From 7.0.0 | 7.3.7 |
| `vite` | npm | From 7.0.0 | 7.3.7 |
| `vite` | npm | From 8.0.0 | 8.1.6 |
| `vite` | npm | From 8.0.0 | 8.1.6 |
| `vite` | npm | From 8.2.0 | 8.2.4 |
| `vite` | npm | From 8.2.0 | 8.2.4 |
| `vite` | npm | From 8.3.0 | 8.3.3 |
| `vite` | npm | From 8.3.0 | 8.3.3 |
| `vite-plus` | npm | All versions | 1.1.0 |
| `vite-plus` | npm | All versions | 1.1.0 |

## How do I fix CVE-2026-112946?

Upgrade vite to a fixed version for your release line: 6.4.4, 7.3.7, 8.1.6 or 8.2.4.

## Is CVE-2026-112946 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112946 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112946 and fix it if it is affected.

What it is: CVE-2026-112946 is a medium-severity vulnerability in vitejs vite, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112946 exists.

Affected packages and fixed versions:
- vite (npm): affected all versions; fixed in 6.4.4
- vite (npm): affected all versions; fixed in 6.4.4
- vite (npm): affected from 7.0.0; fixed in 7.3.7
- vite (npm): affected from 7.0.0; fixed in 7.3.7
- vite (npm): affected from 8.0.0; fixed in 8.1.6
- vite (npm): affected from 8.0.0; fixed in 8.1.6
- vite (npm): affected from 8.2.0; fixed in 8.2.4
- vite (npm): affected from 8.2.0; fixed in 8.2.4
- vite (npm): affected from 8.3.0; fixed in 8.3.3
- vite (npm): affected from 8.3.0; fixed in 8.3.3
- vite-plus (npm): affected all versions; fixed in 1.1.0
- vite-plus (npm): affected all versions; fixed in 1.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112946/ (Markdown: https://insights.sbomify.com/CVE-2026-112946/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112946
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112946
- OSV: https://osv.dev/vulnerability/CVE-2026-112946

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112946/
Summaries are generated and may contain mistakes; the official description above is the record.