CVE-2026-39364: Vite has a `server.fs.deny` bypass with queries
Vite is a frontend tooling framework for JavaScript. From 7.1.0 to before 7.3.2 and 8.0.5, 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. This vulnerability is fixed in 7.3.2 and 8.0.5.
Security readout for executives and security teams
Plain-English summary
A remotely reachable Vite development server may disclose files its deny policy should protect, including environment or certificate files. An unauthenticated requester can trigger the flaw using specially formed query parameters. Exposure could reveal secrets and enable follow-on compromise, although the supplied sources do not establish active exploitation.
Executive priority
Prioritize within the normal high-severity remediation window, accelerating internet-facing or shared-network development servers. Immediately restrict reachability where upgrades cannot be completed. Treat confirmed sensitive-file disclosure as a potential secret exposure requiring incident review and credential rotation.
Technical view
CVE-2026-39364 is a query-handling bypass of Vite's `server.fs.deny` controls. Affected dev servers may return denied files with HTTP 200 when certain transform-related query parameters are supplied. Vite 7.1.0 through 7.3.1, 8.0.0 through 8.0.4, and Vite Plus before 0.1.16 are affected.
Likely exposure
Risk is highest where an affected Vite dev server is reachable from untrusted networks and sensitive files exist within accessible filesystem scope. Production sites serving only built static assets are not identified as affected. Internal dev servers still matter if reachable by compromised devices or other untrusted network users.
Exploitation context
The CVSS 4.0 score is 8.2: network-accessible, low complexity, no privileges, and no user interaction, with high confidentiality impact. The vector includes an attack requirement, so exposure depends on deployment and file availability. The CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation.
Researcher notes
The reported behavior aligns with improper canonicalization and authorization handling represented by CWE-180, CWE-284, and CWE-472. Validation should remain non-destructive and avoid collecting secret contents. The supplied evidence identifies confidentiality impact but does not document integrity or availability impact, public exploit availability, observed attacks, or every deployment condition required.
Mitigation direction
Upgrade Vite 7.x to 7.3.2 or later.
Upgrade Vite 8.x to 8.0.5 or later.
Upgrade Vite Plus to 0.1.16 or later, following vendor guidance.
Prevent development servers from being reachable by untrusted networks.
Rotate exposed secrets if investigation indicates protected files may have been retrieved.
Validation and detection
Inventory Vite and Vite Plus versions across development, CI, preview, and container environments.
Confirm no affected development server is publicly or broadly internally reachable.
Review server logs for unusual query-driven raw, import, URL, or inline file requests.
Verify upgraded servers enforce `server.fs.deny` without exposing sensitive file contents.
Identify potentially exposed credentials or certificates and assess whether rotation is required.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-180: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-180 · source CWE mapping
Incorrect Behavior Order: Validate Before Canonicalize
Incorrect Behavior Order: Validate Before Canonicalize represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
External Control of Assumed-Immutable Web Parameter
External Control of Assumed-Immutable Web Parameter represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.