CVE-2026-25807: CWE-94: Improper Control of Generation of Code ('Code Injection') in TaklaXBR zai-shell
CVE-2026-25807 is a high-severity code injection vulnerability in TaklaXBR's zai-shell versions prior to 9. 0. 3. The flaw exists in the P2P terminal sharing feature, which opens an unauthenticated TCP socket on port 5757. An attacker can connect remotely and send arbitrary system commands if the session is running in --no-ai mode. Execution of these commands depends on the host user approving them without review, bypassing Sentinel safety checks and running with the user's privileges. This vulnerability impacts confidentiality, integrity, and availability, allowing remote code execution without authentication but requiring user interaction. The issue is fixed in version 9. 0. 3.
AI Analysis
Technical Summary
CVE-2026-25807 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the TaklaXBR zai-shell product before version 9.0.3. The vulnerability arises from the P2P terminal sharing feature ('share start'), which opens a TCP socket on port 5757 without any authentication or access control. This design flaw allows any remote attacker to connect to the socket using a simple script and interact with the zai-shell session. When the session is running in '--no-ai' mode, the attacker can send arbitrary system commands. Although command execution requires the host user's approval, the commands bypass all Sentinel safety checks and execute with the user's privileges, potentially leading to full system compromise. The vulnerability affects confidentiality, integrity, and availability by enabling remote code execution (RCE) without authentication. The attack vector is network-based, with low attack complexity and no privileges required. The vulnerability was publicly disclosed on February 9, 2026, with a CVSS v3.1 score of 8.8 (high severity). No known exploits have been observed in the wild, but the risk remains significant due to the ease of exploitation and potential impact. The issue is resolved in zai-shell version 9.0.3, which implements proper authentication and command validation mechanisms for the P2P terminal sharing feature.
Potential Impact
For European organizations, this vulnerability poses a substantial risk, especially those relying on zai-shell for autonomous SysOps management in complex IT environments. Successful exploitation can lead to unauthorized remote code execution, allowing attackers to compromise system confidentiality by accessing sensitive data, integrity by executing malicious commands, and availability by disrupting services. The lack of authentication on the P2P terminal sharing port exposes organizations to remote attacks from anywhere on the internet or internal networks. Critical infrastructure, cloud service providers, and enterprises using zai-shell for automation and repair tasks could face operational disruptions, data breaches, and potential lateral movement within networks. The requirement for user approval reduces but does not eliminate risk, as social engineering or inattentive users may inadvertently approve malicious commands. The vulnerability also undermines trust in automated SysOps agents, potentially delaying incident response and recovery efforts.
Mitigation Recommendations
European organizations should immediately upgrade all instances of zai-shell to version 9.0.3 or later, which addresses the vulnerability by enforcing authentication on the P2P terminal sharing feature and improving command validation. Until upgrades are complete, organizations should disable the P2P terminal sharing feature ('share start') or block inbound TCP connections to port 5757 at network firewalls and host-based firewalls to prevent unauthorized access. Implement strict network segmentation to limit access to management interfaces and monitor network traffic for unusual connections to port 5757. Educate users about the risks of approving commands without review, emphasizing cautious interaction with terminal sharing sessions. Employ endpoint detection and response (EDR) tools to detect anomalous command execution patterns. Regularly audit and review SysOps automation configurations to ensure no unauthorized access paths exist. Finally, maintain up-to-date backups and incident response plans tailored to potential remote code execution scenarios.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy
CVE-2026-25807: CWE-94: Improper Control of Generation of Code ('Code Injection') in TaklaXBR zai-shell
Description
CVE-2026-25807 is a high-severity code injection vulnerability in TaklaXBR's zai-shell versions prior to 9. 0. 3. The flaw exists in the P2P terminal sharing feature, which opens an unauthenticated TCP socket on port 5757. An attacker can connect remotely and send arbitrary system commands if the session is running in --no-ai mode. Execution of these commands depends on the host user approving them without review, bypassing Sentinel safety checks and running with the user's privileges. This vulnerability impacts confidentiality, integrity, and availability, allowing remote code execution without authentication but requiring user interaction. The issue is fixed in version 9. 0. 3.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-25807 is a critical vulnerability classified under CWE-94 (Improper Control of Generation of Code) affecting the TaklaXBR zai-shell product before version 9.0.3. The vulnerability arises from the P2P terminal sharing feature ('share start'), which opens a TCP socket on port 5757 without any authentication or access control. This design flaw allows any remote attacker to connect to the socket using a simple script and interact with the zai-shell session. When the session is running in '--no-ai' mode, the attacker can send arbitrary system commands. Although command execution requires the host user's approval, the commands bypass all Sentinel safety checks and execute with the user's privileges, potentially leading to full system compromise. The vulnerability affects confidentiality, integrity, and availability by enabling remote code execution (RCE) without authentication. The attack vector is network-based, with low attack complexity and no privileges required. The vulnerability was publicly disclosed on February 9, 2026, with a CVSS v3.1 score of 8.8 (high severity). No known exploits have been observed in the wild, but the risk remains significant due to the ease of exploitation and potential impact. The issue is resolved in zai-shell version 9.0.3, which implements proper authentication and command validation mechanisms for the P2P terminal sharing feature.
Potential Impact
For European organizations, this vulnerability poses a substantial risk, especially those relying on zai-shell for autonomous SysOps management in complex IT environments. Successful exploitation can lead to unauthorized remote code execution, allowing attackers to compromise system confidentiality by accessing sensitive data, integrity by executing malicious commands, and availability by disrupting services. The lack of authentication on the P2P terminal sharing port exposes organizations to remote attacks from anywhere on the internet or internal networks. Critical infrastructure, cloud service providers, and enterprises using zai-shell for automation and repair tasks could face operational disruptions, data breaches, and potential lateral movement within networks. The requirement for user approval reduces but does not eliminate risk, as social engineering or inattentive users may inadvertently approve malicious commands. The vulnerability also undermines trust in automated SysOps agents, potentially delaying incident response and recovery efforts.
Mitigation Recommendations
European organizations should immediately upgrade all instances of zai-shell to version 9.0.3 or later, which addresses the vulnerability by enforcing authentication on the P2P terminal sharing feature and improving command validation. Until upgrades are complete, organizations should disable the P2P terminal sharing feature ('share start') or block inbound TCP connections to port 5757 at network firewalls and host-based firewalls to prevent unauthorized access. Implement strict network segmentation to limit access to management interfaces and monitor network traffic for unusual connections to port 5757. Educate users about the risks of approving commands without review, emphasizing cautious interaction with terminal sharing sessions. Employ endpoint detection and response (EDR) tools to detect anomalous command execution patterns. Regularly audit and review SysOps automation configurations to ensure no unauthorized access paths exist. Finally, maintain up-to-date backups and incident response plans tailored to potential remote code execution scenarios.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-05T19:58:01.642Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698a592c4b57a58fa173fd9a
Added to database: 2/9/2026, 10:01:16 PM
Last enriched: 2/17/2026, 9:30:11 AM
Last updated: 3/27/2026, 6:33:44 AM
Views: 85
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.