Skip to content
IoT

CVE-2025-7964

CRITICAL
Critical
EPSS 0.26%Jan 31, 2026

Malformed 802.15.4 MAC Data Request causes Zigbee router to enter non-rejoinable state.

common questions

Is CVE-2025-7964 being exploited?

Not confirmed. CVE-2025-7964 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.

How severe is CVE-2025-7964?

CVE-2025-7964 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-7964?

Not known from our data. No patch reference has been recorded for CVE-2025-7964, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-7964 affect?

CVE-2025-7964 affects Zigbee Coordinator, Zigbee Router, Zigbee end devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-7964?

Apply vendor firmware patch; update Zigbee devices across the network.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Zigbee CoordinatorZigbee RouterZigbee end devices
impact

Router stuck in non-rejoinable state; end devices can't rejoin, causing network downtime.

action required

Patch when possible

affected versions
silabs.com Silicon Labs Zigbee Stack
  • affected<= 4.4.6
  • affected<= 2025.6.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free