dbcve.org
CWE-229Weakness · CWE-229

CVE-2025-7964

CRITICAL · 9.2 CVSS v4.0 Published 2026-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability exists in Zigbee Coordinator firmware where receiving a malformed 802.15.4 MAC Data Request triggers an incorrect 'network leave' transmission to legitimate Zigbee routers. This causes affected routers to become permanently stuck in a non-rejoinable state, preventing end devices from rejoining the network and requiring manual recommissioning for recovery.

MitigationUpdate Zigbee Coordinator firmware to a patched version that properly validates incoming MAC Data Requests before triggering network leave procedures; if unavailable, implement network monitoring to detect router non-rejoinability events and prepare for manual recommissioning procedures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Zigbee Coordinator firmware version
    Access the Zigbee Coordinator device management interface or console and retrieve the firmware version string. This is typically found in the device info, about, or firmware settings section.
    Affected if The installed firmware version matches or precedes the version where the vulnerability was patched (check vendor release notes for version numbers)
  2. Inspect Zigbee router status
    Use the Zigbee network management tool (such as the coordinator's web UI, Zigbee debugger, or CLI tools like zbconsole) to query the status of all associated routers. Look for routers showing a 'non-rejoinable', 'stuck', or 'offline' state that persists across power cycles.
    Affected if Any associated Zigbee router is in a persistent non-rejoinable state despite being powered on and within range
  3. Verify end device rejoining capability
    Attempt to trigger a network rejoin from a known end device by power-cycling it or using a rejoin command. Observe whether the end device successfully rejoins the network or fails with a 'no parent available' or 'join failed' error.
    Affected if End devices fail to rejoin the network after power cycle or rejoin command, reporting no suitable parent available
  4. Examine network leave request logs
    Review the Zigbee Coordinator's event logs, debug logs, or network traffic captures for unexpected or anomalous network leave requests. Look for leave requests that were not initiated by legitimate network management commands.
    Affected if Logs show network leave requests to routers that were not triggered by authorized administrative actions or normal network operations

A defender is affected if their Zigbee Coordinator firmware is vulnerable, and they observe routers stuck in non-rejoinable states or end devices unable to rejoin due to malformed 802.15.4 MAC Data Requests triggering unauthorized leave requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Zigbee Coordinator firmware to a patched version that properly validates incoming MAC Data Requests before triggering network leave procedures; if unavailable, implement network monitoring to detect router non-rejoinability events and prepare for manual recommissioning procedures.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7964 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data