Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-39364: CWE-180: Incorrect Behavior Order: Validate Before Canonicalize in vitejs vite

0
High
VulnerabilityCVE-2026-39364cvecve-2026-39364cwe-180cwe-284
Published: Tue Apr 07 2026 (04/07/2026, 19:12:47 UTC)
Source: CVE Database V5
Vendor/Project: vitejs
Product: vite

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/07/2026, 20:01:46 UTC

Technical Analysis

Vite versions 7.1.0 to before 7.3.2 and 8.0.0 to before 8.0.5 contain a vulnerability (CVE-2026-39364) where the dev server improperly allows access to files that should be blocked by the server.fs.deny setting. This occurs because the server validates file access permissions after canonicalizing the file path, allowing crafted requests with query parameters (?raw, ?import&raw, or ?import&url&inline) to bypass restrictions and retrieve sensitive files with HTTP 200 responses. The issue is categorized under CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize) and CWE-284 (Improper Access Control). The vulnerability has a CVSS 4.0 score of 8.2 (high severity). It is resolved in Vite versions 7.3.2 and 8.0.5.

Potential Impact

An attacker can retrieve sensitive files that should be blocked by the server.fs.deny configuration on the Vite development server, potentially exposing environment variables (.env) or certificate files (*.crt). This unauthorized file access could lead to information disclosure impacting the confidentiality of the affected system. The vulnerability does not require privileges or user interaction but is limited to the development server context.

Mitigation Recommendations

This 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. Since the vulnerability affects specific versions and is resolved in official releases, applying the official patch by upgrading is the recommended mitigation. No vendor advisory content contradicts this guidance. Patch status is confirmed by the version fix information in the description.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-04-06T21:29:17.349Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 69d55f07aaed68159a562944

Added to database: 4/7/2026, 7:46:15 PM

Last enriched: 4/7/2026, 8:01:46 PM

Last updated: 4/8/2026, 12:27:18 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses