# CVE-2026-114278: Unauthenticated Command Injection via kubeconfig Username in che-machine-exec


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-rq96-f9wc-rppm

## What is CVE-2026-114278?

CVE-2026-114278 is a critical vulnerability in Eclipse Che, published on 28 Oct 2026. 

### Official description

The che-machine-exec service constructs a shell command by concatenating user-controlled input (the username and namespace fields from the /exec/init and /exec/config JSON endpoints) into a double-quoted sh -c "echo "..." > ..." invocation without any escaping. When che-machine-exec is run with authentication disabled (its default), any network-reachable attacker can achieve remote code execution in containers che-machine-exec is configured to access, via shell command substitution ($(...) or backticks).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-114278 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114278 is a critical vulnerability in Eclipse Che, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114278 in the wild and no public exploit code.

Affected product: Eclipse Che. 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-114278/ (Markdown: https://insights.sbomify.com/CVE-2026-114278/index.md)
```

## Sources

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

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