dbcve.org
CWE-23Weakness · CWE-23

CVE-2026-8326

CRITICAL · 10.0 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in Remote Spark's SparkView allows attackers to manipulate file paths in the RDP drive redirection feature, enabling reading and writing of arbitrary files across all directories with root privileges. This file system access leads to remote code execution. The vulnerability can be exploited by unauthenticated attackers depending on implementation.

MitigationUpgrade SparkView to build 1127 or later to remediate the path traversal vulnerability. Organizations should immediately inventory all deployments of vulnerable SparkView versions and deploy the patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SparkView installation
    Locate the SparkView installation directory, typically under C:\Program Files\Remote Spark or C:\Program Files (x86)\Remote Spark on Windows, or /opt/sparkview or similar on Linux. Check for sparkview.exe or the SparkView service.
    Affected if SparkView is installed on the system
  2. Determine installed SparkView version
    Right-click sparkview.exe, select Properties, then view the Details tab for Version information. Alternatively, run 'sparkview.exe /version' from command line if supported, or check the Windows Programs and Features list.
    Affected if The version/build number is present and is lower than build 1127
  3. Verify RDP drive redirection is enabled
    Open SparkView configuration or settings panel. Look for RDP settings, specifically the drive redirection or file sharing option. Check if it is set to Enabled or Allow.
    Affected if Drive redirection is enabled in SparkView RDP settings
  4. Check for unauthenticated RDP access
    Review SparkView's security settings for RDP connections. Verify if anonymous or unauthenticated RDP connections are permitted, particularly checking for settings that allow guest or non-authenticated users.
    Affected if Unauthenticated RDP access is permitted in SparkView configuration
  5. Inspect RDP connection logs
    Review SparkView connection logs or Windows Event Viewer logs for RDP connection events, focusing on drive redirection activity. Look for unusual file access patterns or path anomalies.
    Affected if Recent RDP sessions with drive redirection are logged from untrusted sources

A system is affected if SparkView is installed with drive redirection enabled, has a build version below 1127, and allows RDP connections that could be exploited by an unauthenticated attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SparkView to build 1127 or later to remediate the path traversal vulnerability. Organizations should immediately inventory all deployments of vulnerable SparkView versions and deploy the patched version.

Recommended fix High confidence

SparkView build 1127

  1. 1. Identify the currently installed version of Remote Spark SparkView in your environment
  2. 2. Download the latest version of SparkView (build 1127 or later) from the official vendor website at www.remotespark.com
  3. 3. Deploy the upgraded SparkView build 1127 to all affected systems
  4. 4. Verify the upgrade was successful by checking the build version in the SparkView interface or through system inventory
  5. 5. Test that the RDP drive redirection functionality operates normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8326 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data