# CVE-2026-6213: Remote Spark SparkView RCE

> An attacker can bypass local connection checks to achieve arbitrary code execution as root on the server side.

- **Severity:** Critical 10.0 (`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:A`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-m9cx-2hp3-5j6q

## What is CVE-2026-6213?

CVE-2026-6213 is a critical authentication bypass vulnerability in Remote Spark (https://www.remotespark.com/) SparkView, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Remote Spark SparkView before build 1122 allows an attacker to bypasses the local connection check and achieve arbitrary code execution as root on the server side. Depending on implementation the vulnerability can be exploited by an unauthenticated attacker.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-6213?


## How do I fix CVE-2026-6213?

No fix has been published for CVE-2026-6213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6213 being exploited?

There is no known exploitation of CVE-2026-6213 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6213 and fix it if it is affected.

What it is: CVE-2026-6213 is a critical authentication bypass vulnerability in Remote Spark (https://www.remotespark.com/) SparkView, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6213 in the wild and no public exploit code.

Affected product: Remote Spark (https://www.remotespark.com/) SparkView. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6213/ (Markdown: https://insights.sbomify.com/CVE-2026-6213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6213
- OSV: https://osv.dev/vulnerability/CVE-2026-6213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6213/
Summaries are generated and may contain mistakes; the official description above is the record.