CVE-2025-30208: medium-severity vulnerability in vitejs vite
Vite bypasses server.fs.deny when using `?raw??`
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
97Vexday Risk Score
Patch now. It exploitation observed by VulnCheck and has a working public exploit.
ssvc Actcvss 5.3epss 75%
from disclosure to weaponsame day
Published on NVDMar 24
1st PoCMar 21
VulnCheck+35d
What the vendors declare (VEX)
Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.
Red HatVEX document ↗
Affected
2 products (8 components)
Red Hat OpenShift distributed tracing 3 · Red Hat Ansible Automation Platform 2
no_fix_planned: Out of support scope
Not affected
3 products — because the vulnerable code is not present in the product
Red Hat Ansible Automation Platform 2 · Red Hat JBoss Enterprise Application Platform 8 · Red Hat JBoss Enterprise Application Platform Expansion Pack
Vite, a provider of frontend development tooling, has a vulnerability in versions prior to 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10. `@fs` denies access to files outside of Vite serving allow list. Adding `?raw??` or `?import&raw??` to the URL bypasses this limitation and returns the file content if it exists. This bypass exists because trailing separators such as `?` are removed in several places, but are not accounted for in query string regexes. The contents of arbitrary files can be returned to the browser. Only apps explicitly exposing the Vite dev server to the network (using `--host` or `server.host` config option) are affected. Versions 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10 fix the issue.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Affected products
vitejs · vitepublic PoCs found — 59
exploitdbwww.exploit-db.com/exploits/52111unverifiedgithubgithub.com/ThumpBo/CVE-2025-30208-EXP★ 194githubgithub.com/xuemian168/CVE-2025-30208★ 50githubgithub.com/4xura/CVE-2025-30208★ 12githubgithub.com/ThemeHackers/CVE-2025-30208★ 10githubgithub.com/marino-admin/Vite-CVE-2025-30208-Scanner★ 10githubgithub.com/jackieya/ViteVulScan★ 7githubgithub.com/4m3rr0r/CVE-2025-30208-PoC★ 7githubgithub.com/nkuty/CVE-2025-30208-31125-31486-32395★ 5githubgithub.com/On1onss/CVE-2025-30208★ 4githubgithub.com/r0ngy40/CVE-2025-30208-Series★ 3githubgithub.com/L15B04/Exploit-VITE-CVE-2025-30208-CVE-2025-31125★ 2githubgithub.com/keklick1337/CVE-2025-30208-ViteVulnScanner★ 1githubgithub.com/sumeet-darekar/CVE-2025-30208★ 1githubgithub.com/lilil3333/Vite-CVE-2025-30208-EXP★ 1githubgithub.com/TH-SecForge/CVE-2025-30208★ 1githubgithub.com/imbas007/CVE-2025-30208-template★ 1githubgithub.com/Minseo9503/cve-2025-30208★ 0githubgithub.com/cc3305/CVE-2025-30208★ 0githubgithub.com/0xshaheen/CVE-2025-30208★ 0githubgithub.com/HaGsec/CVE-2025-30208★ 0githubgithub.com/Lusensec/CVE-2025-30208★ 0githubgithub.com/sadhfdw129/CVE-2025-30208-Vite★ 0githubgithub.com/iSee857/CVE-2025-30208-PoC★ 0githubgithub.com/HazaVVIP/CVE-2025-30208★ 0githubgithub.com/MiclelsonCN/CVE-2025-30208_POC★ 0vulncheckvulncheck.com/xdb/9ec1c547aa75unverifiedvulncheckvulncheck.com/xdb/d281d302d090unverifiedvulncheckvulncheck.com/xdb/e849c744163eunverifiedvulncheckvulncheck.com/xdb/116a9432fccaunverifiedvulncheckvulncheck.com/xdb/7216ff7bdb87unverifiedvulncheckvulncheck.com/xdb/770c0dc50844unverifiedvulncheckvulncheck.com/xdb/14ccbfa5d418unverifiedvulncheckvulncheck.com/xdb/a619af209c7dunverifiedvulncheckvulncheck.com/xdb/461563839aeeunverifiedvulncheckvulncheck.com/xdb/6320ca04fe07unverifiedvulncheckvulncheck.com/xdb/d25febf46a0dunverifiedvulncheckvulncheck.com/xdb/c84cbb3fd16bunverifiedvulncheckvulncheck.com/xdb/8ae6806b4071unverifiedvulncheckvulncheck.com/xdb/573055c0e76aunverifiedvulncheckvulncheck.com/xdb/108529b531b0unverifiedvulncheckvulncheck.com/xdb/14e5ead281aeunverifiedvulncheckvulncheck.com/xdb/5e5666f6e4b5unverifiedvulncheckvulncheck.com/xdb/bb5065ec0b7aunverifiedvulncheckvulncheck.com/xdb/41f5125956cbunverifiedvulncheckvulncheck.com/xdb/471869748223unverifiedvulncheckvulncheck.com/xdb/e32d7a06be19unverifiedvulncheckvulncheck.com/xdb/90a18ae15449unverifiedvulncheckvulncheck.com/xdb/388dd832b246unverifiedvulncheckvulncheck.com/xdb/5e7ec44b1362unverifiedvulncheckvulncheck.com/xdb/2b49283dffeeunverifiedvulncheckvulncheck.com/xdb/e33919a9052aunverifiedvulncheckvulncheck.com/xdb/6cf8cde60cdeunverifiedvulncheckvulncheck.com/xdb/24952455a76cunverifiedvulncheckvulncheck.com/xdb/548faa8fa166unverifiedvulncheckvulncheck.com/xdb/17f3c0aa6eb8unverifiedvulncheckvulncheck.com/xdb/c07d38ebc777unverifiedvulncheckvulncheck.com/xdb/e32c52f19c5bunverifiedvulncheckvulncheck.com/xdb/80a9c1d50a28unverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — vitejs vite
In the same product, most dangerous first.
CVE-2025-31125MEDIUMVite has a `server.fs.deny` bypassed for `inline` and `raw` with `?import` queryEPSS 74.9%KEVCVE-2025-31486MEDIUMVite allows server.fs.deny to be bypassed with .svg or relative pathsEPSS 40.5%CVE-2026-39363HIGHVite Affected by Arbitrary File Read via Vite Dev Server WebSocketEPSS 3.4%CVE-2023-34092HIGHVite Server Options (server.fs.deny) can be bypassed using double forward-slash (//)EPSS 3.2%CVE-2026-39364HIGHVite has a `server.fs.deny` bypass with queriesEPSS 2.3%CVE-2025-32395MEDIUMVite has an `server.fs.deny` bypass with an invalid `request-target`EPSS 1.8%
References
https://github.com/vitejs/vite/commit/315695e9d97cc6cfa7e6d9e0229fb50cdae3d9f4https://github.com/vitejs/vite/commit/80381c38d6f068b12e6e928cd3c616bd1d64803chttps://github.com/vitejs/vite/commit/807d7f06d33ab49c48a2a3501da3eea1906c0d41https://github.com/vitejs/vite/commit/92ca12dc79118bf66f2b32ff81ed09e0d0bd07cahttps://github.com/vitejs/vite/commit/f234b5744d8b74c95535a7b82cc88ed2144263c1https://github.com/vitejs/vite/security/advisories/GHSA-x574-m823-4x7w