# CVE-2026-26068: emp3r0r Agent-Controlled Metadata to Operator RCE (tmux Command Injection)

> An attacker can execute arbitrary commands on the operator host by injecting malicious metadata during agent check-in.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-h5p4-4xp4-vjpp

## What is CVE-2026-26068?

CVE-2026-26068 is a critical command injection vulnerability in jm33-m0 emp3r0r, published on 12 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

emp3r0r is a stealth-focused C2 designed by Linux users for Linux environments. Prior to 3.21.1, untrusted agent metadata (Transport, Hostname) is accepted during check-in and later interpolated into tmux shell command strings executed via /bin/sh -c. This enables command injection and remote code execution on the operator host. This vulnerability is fixed in 3.21.1.

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

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

It affects 1 product.


Products: Jm33-M0 Emp3r0r.

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

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

## Is CVE-2026-26068 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26068 exists.

## Other vulnerabilities in jm33-m0 emp3r0r

- [CVE-2026-26201](https://insights.sbomify.com/CVE-2026-26201/): emp3r0r Affected by Concurrent Map Access DoS (panic/crash) (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26068 is a critical command injection vulnerability in jm33-m0 emp3r0r, published on 12 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26068 exists.

Affected product: jm33-m0 emp3r0r. 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-26068/ (Markdown: https://insights.sbomify.com/CVE-2026-26068/index.md)
```

## Sources

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

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