Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-26068: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in jm33-m0 emp3r0r

0
Critical
VulnerabilityCVE-2026-26068cvecve-2026-26068cwe-77cwe-78
Published: Thu Feb 12 2026 (02/12/2026, 22:01:23 UTC)
Source: CVE Database V5
Vendor/Project: jm33-m0
Product: emp3r0r

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/20/2026, 09:04:29 UTC

Technical Analysis

The vulnerability identified as CVE-2026-26068 affects the emp3r0r command and control (C2) framework designed primarily for Linux environments. Emp3r0r is a stealth-focused C2 tool used by Linux users to manage agents. Prior to version 3.21.1, the software accepts untrusted metadata from agents during their check-in process, specifically the Transport and Hostname fields. These fields are then directly interpolated into tmux shell command strings executed via /bin/sh -c without proper sanitization or neutralization of special characters. This improper neutralization of special elements (CWE-77 and CWE-78) leads to command injection vulnerabilities, allowing an attacker controlling or spoofing agent metadata to execute arbitrary shell commands on the operator host. The vulnerability does not require authentication and can be triggered remotely, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), and user interaction required (UI:A), with high impact on confidentiality, integrity, and availability, and scope change (S:High). The vulnerability was published on February 12, 2026, and fixed in emp3r0r version 3.21.1. No public exploits have been reported yet, but the critical nature of the flaw and the widespread use of Linux in security operations make it a significant threat.

Potential Impact

The impact of CVE-2026-26068 is severe for organizations using emp3r0r as part of their Linux-based command and control infrastructure. Successful exploitation allows remote attackers to execute arbitrary commands on the operator host, potentially leading to full system compromise, data exfiltration, disruption of operations, or pivoting to other internal systems. Since emp3r0r is often used in stealthy, security-focused environments, compromise of the operator host can undermine entire security monitoring or red team operations. The vulnerability affects confidentiality by exposing sensitive operational data, integrity by allowing unauthorized command execution, and availability by potentially disrupting the C2 infrastructure. Given the network-exploitable nature and lack of required privileges, attackers can leverage this flaw to gain control without needing prior access, increasing the threat to organizations worldwide that rely on this tool.

Mitigation Recommendations

To mitigate CVE-2026-26068, organizations should immediately upgrade emp3r0r to version 3.21.1 or later, where the vulnerability has been fixed. Until patching is possible, restrict network access to the operator host to trusted agents only and implement strict network segmentation to limit exposure. Employ input validation and sanitization on all agent metadata fields before they are used in shell commands, ideally by modifying the source code or applying custom wrappers if upgrading is delayed. Monitor logs for suspicious agent metadata containing shell metacharacters or unexpected command patterns. Use host-based intrusion detection systems (HIDS) to detect anomalous command executions on the operator host. Additionally, consider running the operator host with the least privileges necessary and in a hardened environment to reduce the impact of potential exploitation. Regularly audit and review C2 infrastructure configurations to ensure no untrusted input is executed without proper sanitization.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-10T18:01:31.900Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 698ec65ac9e1ff5ad8f7fbf0

Added to database: 2/13/2026, 6:36:10 AM

Last enriched: 2/20/2026, 9:04:29 AM

Last updated: 3/30/2026, 6:09:49 PM

Views: 406

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses