CVE-2026-25807 json
Unauthenticated Remote Code Execution via P2P Sharing in ZAI-Shell
published 2026-02-09 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-6394
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
ZAI Shell is an autonomous SysOps agent designed to navigate, repair, and secure complex environments. Prior to 9.0.3, the P2P terminal sharing feature (share start) opens a TCP socket on port 5757 without any authentication mechanism. Any remote attacker can connect to this port using a simple socket script. An attacker who connects to a ZAI-Shell P2P session running in --no-ai mode can send arbitrary system commands. If the host user approves the command without reviewing its contents, the command executes directly with the user's privileges, bypassing all Sentinel safety checks. This vulnerability is fixed in 9.0.3.
Patch / fix
- taklaxbr zai_shell 9.0.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 8 mo ago
Exploit prediction
0.71% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/TaklaXBR/zai-shell/security/advisories/GHSA-6pjj-r955-34rr referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- TaklaXBR zai-shell
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/TaklaXBR/zai-shell/commit/a4ea8525d912f55d6e2f09b2869966c52d189a4a
patch
-
github.com
/TaklaXBR/zai-shell/security/advisories/GHSA-6pjj-r955-34rr
exploit, mitigation, vendor-advisory
-
github.com
/TaklaXBR/zai-shell/releases/tag/v9.0.3
product, release-notes
Sources
- CVE List CVE-2026-25807
- NVD CVE-2026-25807
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.