Quick answers
- Is CVE-2026-112947 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112947 being exploited in the wild.
- How severe is CVE-2026-112947?
- Medium severity, with a CVSS score of 4, published 20 October 2026.
- Which products and versions are affected?
- vite-plus (npm) >= 0.2.8, <= 1.0.0, SEMVER:introduced=0.2.8,fixed=1.1.0; Vite 8.2.0 to 8.2.3, 8.3.0 to 8.3.2; Vite >= 8.3.0, <= 8.3.2, SEMVER:introduced=8.3.0,fixed=8.3.3.
- Is there a fix for CVE-2026-112947?
- Yes. vite-plus (npm): upgrade to 1.1.0 or later; Vite: upgrade to 8.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112947 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-112947?
- Check whether you run vite-plus (npm), Vite or Vite at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vite-plus (npm): upgrade to 1.1.0 or later
npm install vite-plus@1.1.0 - Vite: upgrade to 8.3.3 or later
Technical details
The Vite server's WebAssembly plugin load hook processes ?vite-wasm-instance query parameters without applying the fs.serve access controls. After reading the file from disk, failed WebAssembly parsing triggers an error message containing the first 4 bytes of the file. This affects versions 8.2.0–8.2.3 and 8.3.0–8.3.2, and is exploitable via network requests with no authentication required.
Affected products
- Vite Vite 8.2.0 to 8.2.3, 8.3.0 to 8.3.2
Identifiers
- CVE-2026-112947
- GHSA-vfpm-58rq-9qcg
Timeline
- 2026-10-20: disclosed
- 2026-10-20: patched