Skip to main content
VulnerabilityPublished Updated

CVE-2026-39364: vitejs vite · Incorrect Behavior Order: Validate Before Canonicalize

Affects vitejs viteSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 8.2 High : upgrade to 8.0.5 or 7.3.2 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.5, 7.3.2, 0.1.16
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade vite and vitejs/vite to 8.0.5 or 7.3.2; vite-plus to 0.1.16.

Affected software

ProductAffectedFixed in
vitejsviteAffected
  • >=8.0.0 <8.0.5
Fixed in
  • 8.0.5
vitejsviteAffected
  • >=7.1.0 <7.3.2
Fixed in
  • 7.3.2
vitejsvite-plusAffected
  • <0.1.16
Fixed in
  • 0.1.16
npmvitejs/vitepkg:npm/vitejs/viteOther threatsAffected
  • <7.3.2
  • <8.0.5
Fixed in
  • 7.3.2
  • 8.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vulnerability is fixed in Vite versions 7.3.2 and 8.0.5. Users should upgrade to these or later versions to remediate the issue. According to the Red Hat advisory, no alternative mitigation is currently available that meets their criteria for ease of use, applicability, and stability. Therefore, upgrading to a fixed version is the recommended remediation.

Description

### Summary The contents of files that are specified by [`server.fs.deny`](https://vite.dev/config/server-options#server-fs-deny) can be returned to the browser. ### Impact Only apps that match the following conditions are affected: - explicitly exposes the Vite dev server to the network (using `--host` or [`server.host` config option](https://vitejs.dev/config/server-options.html#server-host)) - the sensitive file exists in the allowed directories specified by [`server.fs.allow`](https://vite.dev/config/server-options#server-fs-allow) - the sensitive file is denied with a pattern that matches a file by [`server.fs.deny`](https://vite.dev/config/server-options#server-fs-deny) ### Details On the Vite dev server, files that should be blocked by `server.fs.deny` (e.g., `.env`, `*.crt`) can be retrieved with HTTP 200 responses when query parameters such as `?raw`, `?import&raw`, or `?import&url&inline` are appended. ### PoC 1. Start the dev server: `pnpm exec vite root --host 127.0.0.1 --port 5175 --strictPort` 2. Confirm that `server.fs.deny` is enforced (expect 403): `curl -i http://127.0.0.1:5175/src/.env | head -n 20` <img width="3944" height="1092" alt="image" src="https://github.com/user-attachments/assets/ecb9f2e0-e08f-4ac7-b194-e0f988c4cd4f" /> 3. Confirm that the same files can be retrieved with query parameters (expect 200): <img width="2014" height="373" alt="image" src="https://github.com/user-attachments/assets/76bc2a6a-44f4-4161-ae47-eab5ae0c04a8" />

References

Community reviews

Loading reviews…