# CVE-2025-64126: Zenitel TCIV-3+ OS Command Injection

> Unauthenticated attackers can inject arbitrary OS commands via improper input validation in the Zenitel TCIV-3+ intercom system.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-mq5v-8mqv-63m7

## What is CVE-2025-64126?

CVE-2025-64126 is a critical command injection vulnerability in Zenitel TCIV-3+, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-64126?


## How do I fix CVE-2025-64126?

No fix has been published for CVE-2025-64126 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64126 being exploited?

There is no known exploitation of CVE-2025-64126 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64126 and fix it if it is affected.

What it is: CVE-2025-64126 is a critical command injection vulnerability in Zenitel TCIV-3+, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64126 in the wild and no public exploit code.

Affected product: Zenitel TCIV-3+. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64126/ (Markdown: https://insights.sbomify.com/CVE-2025-64126/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64126
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64126
- OSV: https://osv.dev/vulnerability/CVE-2025-64126

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64126/
Summaries are generated and may contain mistakes; the official description above is the record.