# CVE-2025-7964: Zigbee Router Denial of Service

> Attackers can cause Zigbee routers to enter a non-rejoinable state via malformed MAC requests, requiring manual recommissioning to recover.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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:** 30 Jan 2026
- **Updated:** 30 Jan 2026
- **Also known as:** GHSA-mwv3-x6r9-r9c2

## What is CVE-2025-7964?

CVE-2025-7964 is a critical denial of service vulnerability in silabs.com Silicon Labs Zigbee Stack, published on 30 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

After receiving a 

malformed 802.15.4 MAC Data Request

 the Zigbee Coordinator sends a ‘network leave’ request to Zigbee router resulting in the Zigbee Router getting stuck in a non-rejoinable state. If a suitable parent is not available, the end devices will be unable to rejoin. A manual recommissioning is required to recover the Zigbee Router.

Weakness: CWE-229 (Improper Handling of Values)

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


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

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

## Is CVE-2025-7964 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7964 is a critical denial of service vulnerability in silabs.com Silicon Labs Zigbee Stack, published on 30 Jan 2026. 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-7964 in the wild and no public exploit code.

Affected product: silabs.com Silicon Labs Zigbee Stack. 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-7964/ (Markdown: https://insights.sbomify.com/CVE-2025-7964/index.md)
```

## Sources

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

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