Cloudflare Vite plugin exposes secrets over the built-in dev server
Summary
Note: originally posted on H1 but closed. Cross-posting over to here in abundance of caution instead of a public issue.
When utilising the Cloudflare Vite plugin in its default configuration, all files are exposed by the local dev server, including files in the root directory that contain secret information such as:
.env.dev.vars
PoC
- Create a Workers project that utilises the
@cloudflare/vite-plugin. For example:npm create cloudflare@latest- select Framework Starter -> React
- Add any secret files to test if they're accessible.
echo foobar=secret > .dev.varsfor example - Run
npm run devto start the dev server (after runningnpm ciif necessary to install dependencies) and then hit the following to expose information:
curl http://localhost:5173/.env may expose any secrets in this file
curl http://localhost:5173/.dev.vars may expose any secrets in this file
curl http://localhost:5173/package.json may expose dependencies used by the project, potentially leading to other vulnerabilities
curl http://localhost:5173/README.md may expose internal documentation
Impact
If the vite dev server is exposed on a public network, such as when a user simply uses wrangler to serve their application and doesn't publish to Cloudflare in production, an attacker may be able to acquire secrets that the user doesn't wish to be exposed.
Another common scenario where this could happen is when sharing previews of an application using cloudflared. npm run dev -> share preview with cloudflared -> now all secrets are exposed to the public internet.
Exposing via vite is possible via:
npm run dev -- -- --host 0.0.0.0
The default configuration has no reason to expose information outside of the configured assets directory.
Example:
curl http://somehost/.env may expose secrets
curl http://somehost/.dev.vars may expose secrets
curl http://somehost/package.json may expose dependencies used by the project, potentially leading to other vulnerabilities
curl http://somehost/README.md may expose internal documentation
etc.
Information disclosure to anyone on the same network, or if the dev server is exposed such as via cloudflared as explored here: https://github.com/cloudflare/workers-sdk/discussions/3455#discussioncomment-6165773
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | @cloudflare/vite-plugin | < 1.6.0 | 1.6.0 |
References
- https://github.com/cloudflare/workers-sdk/security/advisories/GHSA-4pfg-2mw5-f8jx
- https://nvd.nist.gov/vuln/detail/CVE-2025-59427
- https://github.com/cloudflare/workers-sdk/commit/0e500720bf70016fa4ea21fc8959c4bd764ebc38
- https://hackerone.com/reports/3117837
- https://github.com/cloudflare/workers-sdk
- https://github.com/cloudflare/workers-sdk/discussions/3455#discussioncomment-6165773
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P- Weakness (CWE)
CWE-200- Platform
- npm
- Package
@cloudflare/vite-plugin- Disclosed
- 08.07.2025
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-4pfg-2mw5-f8jx - CC BY 4.0
Vulnerability history: @cloudflare/vite-plugin
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
This is the only known vulnerability of this package.
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.