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.
CVE-2025-30208
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.3 because EPSS predicted 75% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.
Also known asEUVD-2025-8079 (ENISA EUVD) · GHSA-x574-m823-4x7w (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 75%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 8.3HIGHhigh confidence
- EG Risk
- 54EG Risk 54/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation75% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 75%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.3 MEDIUM): a likelihood of exploitation, not impact.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 75% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
March 24, 2025
Last Modified
September 23, 2025
Advisory Details (6)
Auto-updated Oct 18, 2026server.fs.deny bypassed when using `?raw??` · Advisory · vitejs/vite · GitHub
https://github.com/vitejs/vite/security/advisories/GHSA-x574-m823-4x7wcommit f234b5744d8b (vitejs/vite)
Fix landed in vitejs/vite commit f234b5744d8b — awaiting tagged release
https://github.com/vitejs/vite/commit/f234b5744d8b74c95535a7b82cc88ed2144263c1commit 92ca12dc7911 (vitejs/vite)
Fix landed in vitejs/vite commit 92ca12dc7911 — awaiting tagged release
https://github.com/vitejs/vite/commit/92ca12dc79118bf66f2b32ff81ed09e0d0bd07cacommit 807d7f06d33a (vitejs/vite)
Fix landed in vitejs/vite commit 807d7f06d33a — awaiting tagged release
https://github.com/vitejs/vite/commit/807d7f06d33ab49c48a2a3501da3eea1906c0d41commit 80381c38d6f0 (vitejs/vite)
Fix landed in vitejs/vite commit 80381c38d6f0 — awaiting tagged release
https://github.com/vitejs/vite/commit/80381c38d6f068b12e6e928cd3c616bd1d64803ccommit 315695e9d97c (vitejs/vite)
Fix landed in vitejs/vite commit 315695e9d97c — awaiting tagged release
https://github.com/vitejs/vite/commit/315695e9d97cc6cfa7e6d9e0229fb50cdae3d9f4Patch Availability(5)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | vite @ 6.2.3 (fixes >= 6.2.0, < 6.2.3) | — | ghsa |
| npm | vite @ 6.1.2 (fixes >= 6.1.0, < 6.1.2) | — | ghsa |
| npm | vite @ 6.0.12 (fixes >= 6.0.0, < 6.0.12) | — | ghsa |
| npm | vite @ 5.4.15 (fixes >= 5.0.0, < 5.4.15) | — | ghsa |
| npm | vite @ 4.5.10 (fixes < 4.5.10) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| vite | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 26× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 85 of 99 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 100 are merged into the row they repeat. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 08:07 UTCGHSA enrichmentGHSA-x574-m823-4x7w · GitHub severity MODERATE · GitHub CVSS 5.3
- 2026-11-01 08:07 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-27 11:56 UTCEG score recompute
- 2026-10-26 16:29 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-25 16:37 UTCEG score recompute
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-22 16:32 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-18 18:24 UTCEG score recompute
- 2026-10-18 05:40 UTCEG score recompute
- 2026-10-17 16:32 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-13 16:32 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-12 17:13 UTCEG score recompute
- 2026-10-11 20:44 UTCEG score recompute
- 2026-10-11 18:55 UTCEG score recompute
- 2026-10-11 15:33 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 75% · 99th percentile
Show 60 moreShow fewer
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-10-02 19:10 UTCOSV refresh
- 2026-10-01 19:49 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-16 05:13 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-13 16:46 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-13 16:43 UTCOSV refresh
- 2026-09-12 15:00 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-10 09:33 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-09-01 13:53 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-30 01:21 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-25 18:09 UTCOSV refresh
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-12 13:50 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-09 10:14 UTCOSV refresh
- 2026-08-07 16:26 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-30 16:27 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-28 15:35 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-26 14:53 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-25 14:17 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-24 14:17 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-24 11:11 UTCOSV refresh
- 2026-07-23 02:52 UTCEG score recompute▼ 0.70
- 2026-07-22 14:07 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-20 17:07 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-16 17:02 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-15 16:57 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-13 06:12 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-12 05:46 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-11 08:27 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-08 15:14 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-07 06:51 UTCOSV refresh
- 2026-07-06 16:26 UTCEPSS rescoreEPSS 75% · 99th percentile
- 2026-07-04 06:30 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-07-01 15:06 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-06-30 23:21 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-06-29 14:06 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-06-28 04:55 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-06-25 13:49 UTCEPSS rescoreEPSS 77% · 99th percentile
- 2026-06-24 14:04 UTCEPSS rescoreEPSS 79% · 99th percentile
- 2026-06-23 21:32 UTCEPSS rescoreEPSS 79% · 99th percentile
- 2026-06-18 17:43 UTCOSV refresh
- 2026-06-17 17:52 UTCEPSS rescoreEPSS 79% · 99th percentile
- 2026-06-15 17:48 UTCEPSS rescoreEPSS 79% · 99th percentile
- 2026-06-13 23:00 UTCEPSS rescoreEPSS 90% · 99th percentile
Publicly available exploits
(14 references, 10 shown)Public exploit code is referenced for this CVE (1 Exploit-DB entry, 9 GitHub PoCs), as are 1 Nuclei detection template, 3 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- GitHub PoCThemeHackers/CVE-2025-30208Published Jun 27, 2025
CVE‑2025‑30208 is a medium-severity arbitrary file read vulnerability in the Vite development server (a popular frontend build tool)
Open source ↗ - Open source ↗GitHub PoCnkuty/CVE-2025-30208-31125-31486-32395Published May 29, 2025
- GitHub PoCr0ngy40/CVE-2025-30208-SeriesPublished Apr 24, 2025
Analysis of the Reproduction of CVE-2025-30208 Series Vulnerabilities
Open source ↗ - Exploit-DBEDB-52111Published Apr 3, 2025
Vite 6.2.2 - Arbitrary File Read
Open source ↗ - GitHub PoC4m3rr0r/CVE-2025-30208-PoCPublished Apr 3, 2025
CVE-2025-30208 - Vite Arbitrary File Read PoC
Open source ↗ - GitHub checkerjackieya/ViteVulScanPublished Mar 31, 2025
针对CVE-2025-30208和CVE-2025-31125的漏洞利用
Open source ↗ - GitHub PoC4xura/CVE-2025-30208Published Mar 27, 2025
A PoC of the exploit script for the Arbitrary File Read vulnerability of Vite /@fs/ Path Traversal in the transformMiddleware (CVE-2025-30208).
Open source ↗ - GitHub PoCOn1onss/CVE-2025-30208Published Mar 27, 2025
This exploit is for educational and ethical security testing purposes only. The use of this exploit against targets without prior mutual consent is illegal, and the developer disclaims any liability for misuse or damage caused by this exploit.
Open source ↗ - Nucleihttp/cves/2025/CVE-2025-30208.yamlPublished Mar 27, 2025
Vite - Arbitrary File Read
Open source ↗ - GitHub checkermarino-admin/Vite-CVE-2025-30208-ScannerPublished Mar 26, 2025
CVE-2025-30208-EXP 任意文件读取
Open source ↗
Related CVEs(same product + same CWE)
Same product
10 shownnpm:vite
Frequently asked(5)
What is CVE-2025-30208?
When was the CVE record for CVE-2025-30208 published?
Is CVE-2025-30208 actively exploited?
What is the CVSS score of CVE-2025-30208?
How do I remediate CVE-2025-30208?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30208
Is Your Infrastructure Affected by CVE-2025-30208?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.