CVE-2025-64126: Zenitel TCIV-3+ · OS Command Injection
Affects Zenitel TCIV-3+Source CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.4% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Zenitel TCIV-3+ | Affected
| Fixed in– |
AI-suggested
1. Immediately restrict network access to Zenitel TCIV-3+ devices by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks. 2. Monitor network traffic for unusual or malformed input targeting the vulnerable parameter, using IDS/IPS systems with custom signatures if possible. 3. Employ application-layer filtering or proxy solutions to validate and sanitize inputs before they reach the device. 4. Engage with Zenitel support to obtain timelines for patches or firmware updates addressing the vulnerability and apply them promptly once available. 5. Conduct thorough audits of all Zenitel TCIV-3+ deployments to identify exposed devices and ensure they are not accessible from the internet or untrusted networks. 6. Implement strict access control policies and multi-factor authentication for management interfaces to reduce risk of unauthorized access. 7. Prepare incident response plans specific to potential exploitation scenarios involving these devices. 8. Consider temporary device replacement or disabling vulnerable features if patching is delayed and risk is unacceptable.
Description
An OS command injection vulnerability exists due to improper input validation. The application accepts a parameter directly from user input without verifying it is a valid IP address or filtering potentially malicious characters. This could allow an unauthenticated attacker to inject arbitrary commands.