CVE-2026-8326

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-33281 (ENISA EUVD) · GHSA-fhv3-q37g-rjx5 (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

Update to build 1127 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)) — apply it.

Path traversal vulnerability in Remote Spark (https://www.Remotespark.Com/) SparkView allows reading and writing arbitrary files in all directories as root. This leads to RCE. The affected component is the RDP drive redirection.  Depending on implementation, the vulnerability can be exploited by an unauthenticated attacker.

This issue affects SparkView: before build 1127.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 total (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: Update to build 1127 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 3 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).

Update to build 1127 (from the CVE record's solution, Switzerland National Cyber Security Centre (NCSC)). 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 total (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)3 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 total (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

May 29, 2026

Last Modified

July 21, 2026

References (1)

Vendor Advisories for CVE-2026-8326(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 74× 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 99 of 481 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 382 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 22:13 UTCEG score recompute
  2. 2026-11-01 22:13 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-31 21:26 UTCEG score recompute
  5. 2026-10-31 21:26 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-30 20:41 UTCEG score recompute
  8. 2026-10-30 20:41 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  9. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-29 19:56 UTCEG score recompute
  11. 2026-10-29 19:56 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  12. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-28 19:12 UTCEG score recompute
  14. 2026-10-28 19:12 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  15. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-27 18:13 UTCEG score recompute
  17. 2026-10-27 18:13 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-26 17:28 UTCEG score recompute
  20. 2026-10-26 17:27 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-25 16:18 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  24. 2026-10-25 13:57 UTCEG score recompute
  25. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 74 more
  1. 2026-10-24 15:32 UTCEG score recompute
  2. 2026-10-24 15:32 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  3. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-23 14:48 UTCEG score recompute
  5. 2026-10-23 14:48 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-22 14:01 UTCEG score recompute
  8. 2026-10-22 14:00 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  9. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-21 13:15 UTCEG score recompute
  11. 2026-10-21 13:14 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  12. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-20 12:07 UTCEG score recompute
  14. 2026-10-20 12:07 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-19 11:18 UTCEG score recompute
  17. 2026-10-19 11:18 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-18 08:40 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  20. 2026-10-18 03:07 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-17 07:53 UTCEG score recompute
  23. 2026-10-17 07:53 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-10-16 07:07 UTCEG score recompute
  26. 2026-10-16 07:07 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  27. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-10-15 05:54 UTCEG score recompute
  29. 2026-10-15 05:54 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  30. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-10-14 01:32 UTCEG score recompute
  32. 2026-10-14 01:32 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  33. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-10-12 21:43 UTCEG score recompute
  35. 2026-10-12 21:43 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  36. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-10-12 14:54 UTCEG score recompute
  38. 2026-10-12 05:18 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  39. 2026-10-11 19:19 UTCEG score recompute
  40. 2026-10-11 16:35 UTCEG score recompute
  41. 2026-10-11 13:53 UTCEG score recompute
  42. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  43. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  47. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  52. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  53. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  54. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  56. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  58. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  61. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  62. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  63. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  64. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  65. 2026-09-14 06:28 UTCEG score recompute
  66. 2026-09-14 06:28 UTCGHSA enrichmentGHSA-fhv3-q37g-rjx5 · GitHub severity CRITICAL
  67. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  68. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  69. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  70. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  73. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  74. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile

Frequently asked(5)

What is CVE-2026-8326?
CVE-2026-8326 is a critical-severity vulnerability; its CVE record was published on May 29, 2026. Path traversal vulnerability in Remote Spark (https://www.Remotespark.Com/) SparkView allows reading and writing arbitrary files in all directories as root. This leads to RCE. The affected component is the RDP drive redirection. Depending on implementation, the vulnerability can be exploited by an…
When was the CVE record for CVE-2026-8326 published?
The CVE record for CVE-2026-8326 was published on May 29, 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 July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-8326 actively exploited?
CVE-2026-8326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8326?
CVE-2026-8326 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-8326?
The CVE record's solution for CVE-2026-8326, written by its CNA Switzerland National Cyber Security Centre (NCSC), names the fix: "Update to build 1127". The vendor advisories EchelonGraph has for CVE-2026-8326 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8326

Explore →

Is Your Infrastructure Affected by CVE-2026-8326?

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