Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-118662medium6.9

Vite: `server.fs.deny` bypassed with queries

Impact

Vite dev server versions 6.4.4 to less than 6.4.5 are affected by a bypass of the `server.fs.deny` configuration, allowing access to sensitive files when query parameters are used. The vulnerability requires the Vite dev server to be exposed to the network and the sensitive file to be in an allowed directory. The impact is limited to apps that match specific conditions.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Affected range Recorded fix
From 6.4.4 before 6.4.5Semantic versions6.4.5

Version evidence: OSV · GHSA-8g5g-mxqh-grgj

View original version evidence (1 explicit versions)

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

vitejs · GitHub_M

vite

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 6.4.4, < 6.4.5

unaffected

unknown

Other versions: unknown

Original source description

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser. This is the same as https://github.com/vitejs/vite/security/advisories/GHSA-v2wj-q39q-566r.

Impact

Only apps that match the following conditions are affected:

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.

For the fix for https://github.com/vitejs/vite/security/advisories/GHSA-rq7h-c2jc-7f22, v6.4.4 back-ported https://github.com/vitejs/vite/pull/20410. But while that PR requires https://github.com/vitejs/vite/pull/22160 for https://github.com/vitejs/vite/security/advisories/GHSA-v2wj-q39q-566r, https://github.com/vitejs/vite/pull/22160 wasn't back-ported together causing v6 vulnerable to https://github.com/vitejs/vite/security/advisories/GHSA-v2wj-q39q-566r.

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-118662

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-180 ↗

CWE-180: Incorrect Behavior Order: Validate Before Canonicalize

GitHub_M

Related →
CWE-284 ↗

CWE-284: Improper Access Control

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-28

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

7 sources