Authenticated C2 crash via unsynchronized shared map access
Published Feb 19, 2026 · Updated Feb 19, 2026
Race conditions in emp3r0r before 3.21.2 allow remote authenticated users to crash the C2 server through concurrent control traffic. The OPERATORS, PortFwds, and FTPStreams maps mix iteration, lookup, insertion, and deletion across goroutines without a consistent lock policy. Exploitation requires active operator sessions plus rapid session churn alongside message-tunnel or file-transfer traffic; the Go panic exits the C2 process.
Summary
What happened
Race conditions in emp3r0r before 3.21.2 allow remote authenticated users to crash the C2 server through concurrent control traffic. The OPERATORS, PortFwds, and FTPStreams maps mix iteration, lookup, insertion, and deletion across goroutines without a consistent lock policy. Exploitation requires active operator sessions plus rapid session churn alongside message-tunnel or file-transfer traffic; the Go panic exits the C2 process.
The record
- CVE
- CVE-2026-26201
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- jm33-m0
- Product
- emp3r0r
- Classifications
- CWE-663, CWE-362, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.21.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream concurrent-session crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo