# CVE-2025-64129: Zenitel TCIV-3+ Out-of-bounds Write

> A remote attacker can crash the Zenitel TCIV-3+ intercom device via an out-of-bounds write vulnerability.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-prm5-j94f-rr92

## What is CVE-2025-64129?

CVE-2025-64129 is a high-severity memory corruption vulnerability in Zenitel TCIV-3+, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Zenitel TCIV-3+ is vulnerable to an out-of-bounds write 
vulnerability, which could allow a remote attacker to crash the device.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2025-64129 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64129 is a high-severity memory corruption vulnerability in Zenitel TCIV-3+, published on 26 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64129 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-64129/ (Markdown: https://insights.sbomify.com/CVE-2025-64129/index.md)
```

## Sources

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

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