CVE-2026-118662

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-112469 (ENISA EUVD) · GHSA-8g5g-mxqh-grgj (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vite is a frontend tooling framework for JavaScript. From 6.4.4 until 6.4.5, the Vite development server can evaluate server.fs.deny before stripping loader query parameters such as ?raw, ?import&raw, or ?import&url&inline. When the development server is exposed to the network and a sensitive file is inside server.fs.allow but matched by server.fs.deny, an unauthenticated attacker can append one of these queries and retrieve the denied file. This issue is fixed in version 6.4.5.

CVSS
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/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)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
22nd
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 (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 28, 2026

Last Modified

November 3, 2026

Advisory Details (5)

Auto-updated Nov 3, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

`server.fs.deny` bypassed with queries for v6 · Advisory · vitejs/vite · GitHub

https://github.com/vitejs/vite/security/advisories/GHSA-8g5g-mxqh-grgj
GitHub release Patch Available

v6.4.5

Patch available: vitejs/vite v6.4.5

https://github.com/vitejs/vite/releases/tag/v6.4.5
GitHub pull request Patch Available

fix: check `server.fs` after stripping query as well (#22160)

Patch available: vitejs/vite v6.4.5 (PR #23855 merged 2026-10-21)

https://github.com/vitejs/vite/pull/23855
GitHub pull request Patch Available

fix: check `server.fs` after stripping query as well

Patch available: vitejs/vite v8.1.4 (PR #22160 merged 2026-04-06)

https://github.com/vitejs/vite/pull/22160
GitHub commit Patch Available

commit 91e40d7bf977 (vitejs/vite)

Patch available: vitejs/vite v6.4.5 (contains commit 91e40d7bf977)

https://github.com/vitejs/vite/commit/91e40d7bf9777057bbd31c3eb036a54c9465697e

Vendor Advisories for CVE-2026-118662(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmvite @ 6.4.5 (fixes = 6.4.4)—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)
PackageVulnerable rangeFix by version rangeDependents
vite6.4.4
  • 6.4.4 up to 6.4.5: fixed in 6.4.5
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 21× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-11-11 06:55 UTCEchelonGraph re-scored
  4. 2026-11-11 06:55 UTCGHSA enrichmentGHSA-8g5g-mxqh-grgj · GitHub severity MODERATE
  5. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-11-04 01:48 UTCEchelonGraph re-scored
  13. 2026-11-04 01:48 UTCGHSA enrichmentGHSA-8g5g-mxqh-grgj · GitHub severity MODERATE
  14. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-11-03 00:27 UTCEchelonGraph re-scored
  16. 2026-11-03 00:27 UTCGHSA enrichmentGHSA-8g5g-mxqh-grgj · GitHub severity MODERATE
  17. 2026-11-03 00:10 UTCEchelonGraph re-scored
  18. 2026-11-03 00:10 UTCGHSA enrichmentGHSA-8g5g-mxqh-grgj · GitHub severity MODERATE
  19. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  20. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-28 21:27 UTCEchelonGraph re-scored
  25. 2026-10-28 21:01 UTCENISA EUVD ID recordedEUVD-2026-112469 · Source: ENISA EUVD
Show 2 more
  1. 2026-10-28 20:46 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  2. 2026-10-28 20:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-118662?
CVE-2026-118662 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. Vite is a frontend tooling framework for JavaScript. From 6.4.4 until 6.4.5, the Vite development server can evaluate server.fs.deny before stripping loader query parameters such as ?raw, ?import&raw, or ?import&url&inline. When the development server is exposed to the network and a sensitive file…
When was the CVE record for CVE-2026-118662 published?
The CVE record for CVE-2026-118662 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-118662 actively exploited?
CVE-2026-118662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118662?
CVE-2026-118662 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118662?
A fix for CVE-2026-118662 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118662 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118662

Explore →

Is Your Infrastructure Affected by CVE-2026-118662?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.