fix: update vite to 7.3.2 to resolve server.fs.deny bypass (GHSA-v2wj-q39q-566r)#751
Closed
fix: update vite to 7.3.2 to resolve server.fs.deny bypass (GHSA-v2wj-q39q-566r)#751
Conversation
Copilot
AI
changed the title
[WIP] Fix Vite server.fs.deny bypass vulnerability
fix: update vite to 7.3.2 to resolve server.fs.deny bypass (GHSA-v2wj-q39q-566r)
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Pins transitive dependency
viteto 7.3.2 via pnpm overrides to resolve CVE-2026-39364 — a high-severity bypass ofserver.fs.denyusing query parameters (?raw,?import&raw,?import&url&inline).What
pnpm.overridesin rootpackage.jsonto pinviteto7.3.27.3.0remainWhy
Dependabot flagged
vite@7.3.0for GHSA-v2wj-q39q-566r. Files blocked byserver.fs.denycould be served with HTTP 200 when query parameters were appended.How
viteis not a direct dependency — it's pulled in transitively byvitestandfumadocs-mdx. A pnpm override is the least disruptive way to force resolution to the patched version without touching any workspace package manifests.Reachability Assessment
Not reachable — high confidence. This project uses Next.js for its web app; Vite is only present as a transitive dep for the test runner (
vitest) andfumadocs-mdx. No usage ofserver.host,server.fs.deny, or--hostexists anywhere in the codebase. The vulnerable code path (Vite dev server file serving) is never exercised. Update is to satisfy vulnerability scanners.Related Issues
Type of Change
Packages Affected
@ohcnetwork/leaderboard-api@leaderboard/plugin-runner@leaderboard/plugin-dummycreate-leaderboard-plugincreate-leaderboard-data-repoleaderboard-web(Next.js app)/docs)Quality Checklist
Core Requirements (Mandatory)
Version Management
pnpm changesetfor version-tracked packagesTesting
pnpm testruns successfullypnpm test:coverageto verifyBuild & Type Safety
pnpm build:packagescompletes without errorspnpm --filter <package> typecheck)pnpm --filter leaderboard-web lint(for web app changes)Documentation
/docs) updated if neededPlugin-Specific Requirements
packages/api/src/types.tsScreenshots / Videos
N/A — dependency-only change, no UI impact.
Before
After
Original prompt
This section details the Dependabot vulnerability alert you should resolve
<alert_title>Vite:
server.fs.denybypassed with queries</alert_title><alert_description>### Summary
The contents of files that are specified by
server.fs.denycan be returned to the browser.Impact
Only apps that match the following conditions are affected:
--hostorserver.hostconfig option)server.fs.allowserver.fs.denyDetails
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&inlineare appended.PoC
pnpm exec vite root --host 127.0.0.1 --port 5175 --strictPortserver.fs.denyis enforced (expect 403):curl -i http://127.0.0.1:5175/src/.env | head -n 20high
https://github.com/vitejs/vite/security/advisories/GHSA-v2wj-q39q-566r https://github.com/vitejs/vite/pull/22160 https://github.com/vitejs/vite/commit/a9a3df299378d9cbc5f069e3536a369f8188c8ff https://github.com/vitejs/vite/releases/tag/v7.3.2 https://github.com/vitejs/vite/releases/tag/v8.0.5 https://nvd.nist.gov/vuln/detail/CVE-2026-39364 https://github.com/advisories/GHSA-v2wj-q39q-566rGHSA-v2wj-q39q-566r, CVE-2026-39364
vite
npm
<vulnerable_versions>7.3.0</vulnerable_versions>
<patched_version>7.3.2</patched_version>
<manifest_path>pnpm-lock.yaml</manifest_path>
<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the...