CVE-2026-112947

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd 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
Trending — 4 sources updated this week

Also known asEUVD-2026-105135 (ENISA EUVD) · GHSA-vfpm-58rq-9qcg (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Vite is a frontend tooling framework for JavaScript. From 8.2.0 until 8.2.4 and 8.3.3, the first 4 bytes of files outside of server.fs setting can be returned to the browser by a request containing ?vite-wasm-instance. Requests containing the ?vite-wasm-instance query are handled by the internal Wasm plugin's load hook. The hook removes the query and reads the resulting path directly from disk, but the server.fs checks were not applied. After reading the file, Vite attempts to parse it as WebAssembly. When that parse fails, Node and deno throws an error that contains the first 4 bytes of the file. This vulnerability is fixed in 8.2.4 and 8.3.3.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 every mission impact level.
Exploitation none (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
0.5%
EPSS %ILE
42nd
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.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% 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 every mission impact level.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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (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

October 20, 2026

Last Modified

October 21, 2026

Advisory Details (4)

Auto-updated Oct 20, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
GitHub commit Patch Available

commit ba8b7ab43b4a (vitejs/vite)

Patch available: vitejs/vite v8.3.3 (contains commit ba8b7ab43b4a)

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

commit b6c6d2fb3f85 (vitejs/vite)

Patch available: vitejs/vite v8.2.4 (contains commit b6c6d2fb3f85)

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

fix(server): check `fs.serve` for `?vite-wasm-instance`

Patch available: vitejs/vite v8.3.3 (PR #23655 merged 2026-10-06)

https://github.com/vitejs/vite/pull/23655
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

First 4 bytes of files outside of `server.fs` setting is exposed by `?vite-wasm-instance` · Advisory · vitejs/vite · GitHub

https://github.com/vitejs/vite/security/advisories/GHSA-vfpm-58rq-9qcg

Vendor Advisories for CVE-2026-112947(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmvite @ 8.3.3 (fixes >= 8.3.0, <= 8.3.2)—ghsa
npmvite @ 8.2.4 (fixes >= 8.2.0, <= 8.2.3)—ghsa
npmvite-plus @ 1.1.0 (fixes >= 0.2.8, <= 1.0.0)—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

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
vite—
  • 8.3.0 up to 8.3.3: fixed in 8.3.3
  • 8.2.0 up to 8.2.4: fixed in 8.2.4
—
vite-plus—
  • 0.2.8 up to 1.1.0: fixed in 1.1.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 22× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-vfpm-58rq-9qcg · GitHub severity MODERATE
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-29 15:13 UTCEG score recompute
  8. 2026-10-29 09:55 UTCOSV refresh
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-25 14:51 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-21 16:31 UTCEG score recompute
  19. 2026-10-21 16:01 UTCEG score recompute
  20. 2026-10-20 16:28 UTCEG score recompute
  21. 2026-10-20 15:24 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  22. 2026-10-20 15:21 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-112947?
CVE-2026-112947 is a medium-severity vulnerability; its CVE record was published on October 20, 2026. Vite is a frontend tooling framework for JavaScript. From 8.2.0 until 8.2.4 and 8.3.3, the first 4 bytes of files outside of server.fs setting can be returned to the browser by a request containing ?vite-wasm-instance. Requests containing the ?vite-wasm-instance query are handled by the internal…
When was the CVE record for CVE-2026-112947 published?
The CVE record for CVE-2026-112947 was published on October 20, 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 October 21, 2026; the record at its source may have been updated since.
Is CVE-2026-112947 actively exploited?
CVE-2026-112947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112947?
CVE-2026-112947 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112947?
A fix for CVE-2026-112947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112947 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-112947

Explore →

Is Your Infrastructure Affected by CVE-2026-112947?

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

Book a Demo →Browse All CVEs