Answer in brief
CVE-2026-112945 records a Low severity (CVSS 2.1) vulnerability in Vite: Cross origin script execution through Vite custom middleware. The current sources do not mark it as known exploited. The current feed maps vitejs/vite (generic), vitejs/vite-plus (generic). 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 2.1. 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 vitejs/vite (generic), vitejs/vite-plus (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vitejs/vitegeneric | >=8.3.0 <8.3.3 || >=8.2.0 <8.2.4 || >=8.0.0 <8.1.6 || >=7.0.0 <7.3.7 || <6.4.4 | 6.4.4, 8.3.3, 8.2.4, 8.1.6, 7.3.7 |
| vitejs/vite-plusgeneric | <1.1.0 | 1.1.0 |
Published upstream
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 20, 2026
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, applications using custom middleware are vulnerable when they pass an unchanged browser request URL to server.transformIndexHtml. getHtmlFilename uses the query-bearing request URL to resolve an existing local file while preserving attacker-supplied leading slashes in the generated proxy module URL. If the transformed HTML contains an inline module script and a victim browser loads the crafted development-server page, the leading double slash makes the browser fetch and execute an attacker-controlled module in the Vite-served page. This execution can expose sensitive page data or permit critical actions available to the affected application. This issue is fixed in versions 6.4.4, 7.3.7, 8.1.6, 8.2.4, and 8.3.3.
Quoted source text, attributed separately from HOL analysis.