fix(docs): bump vite to 7.3.2 (CVE-2026-39364, GHSA-v2wj-q39q-566r)

[Copilot]

Vite ≤ 7.1.x allows server.fs.deny to be bypassed by appending query params (?raw, ?import&raw, ?import&url&inline), leaking denied files with HTTP 200. Fixed in 7.3.2.

Changes

• docs/package.json — added "overrides": { "vite": "^7.3.2" } to force the patched version across all transitive consumers; @vuepress/bundler-vite@2.0.0-rc.26 pins "vite": "~7.1.9" so a direct version bump alone is insufficient. Also tightened the direct vite devDependency from >=6.4.1 → ^7.3.2.

  "overrides": {
    "vite": "^7.3.2"
  }

• docs/package-lock.json — regenerated; node_modules/vite now resolves to 7.3.2.

Reachability Assessment

Not reachable — high confidence. The advisory requires the dev server to be explicitly exposed to the network (--host / server.host). Neither the docs/.vitepress/config.mts nor any npm script sets server.host or passes --host; no server.fs.deny/server.fs.allow customizations exist. The Vite server is local-only documentation tooling. Update is defense-in-depth / scanner compliance.

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Vite: server.fs.deny bypassed with queries</alert_title>
<alert_description>### Summary

The contents of files that are specified by 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)
• the sensitive file exists in the allowed directories specified by server.fs.allow
• the sensitive file is denied with a pattern that matches a file by 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
   
3. Confirm that the same files can be retrieved with query parameters (expect 200):
   </alert_description>

high
GHSA-v2wj-q39q-566r, CVE-2026-39364
vite
npm
<vulnerable_versions>7.1.11</vulnerable_versions>
<patched_version>7.3.2</patched_version>
<manifest_path>docs/package-lock.json</manifest_path>

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-566r

<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 ...

• Resolves Azure-Samples/azure-ai-travel-agents alert #289