CVE-2025-7964: silabs.com Silicon Labs Zigbee Stack · Improper Handling of Values
Affects silabs.com Silicon Labs Zigbee StackSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| silabs.comSilicon Labs Zigbee Stack | Affected
| Fixed in– |
| silabs.comSilicon Labs Zigbee Stack | Affected
| Fixed in– |
GitHubGSDKpkg:github/GSDKOther threats | Affected
| Fixed in– |
GitHubSiSDKpkg:github/SiSDKOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Implement network segmentation to isolate Zigbee Coordinator devices from untrusted or less secure network segments, reducing exposure to malformed packets. 2. Deploy intrusion detection or anomaly detection systems capable of identifying malformed 802.15.4 MAC frames or unusual 'network leave' commands within Zigbee traffic. 3. Monitor Zigbee network health continuously to detect Router disconnections promptly and initiate rapid response procedures. 4. Prepare operational playbooks for manual recommissioning of Zigbee Routers to minimize downtime in case of exploitation. 5. Engage with Silicon Labs for updates or patches and apply them promptly once available. 6. Where possible, employ Zigbee stack versions with improved input validation or alternative vendor stacks not affected by this vulnerability. 7. Limit physical and network access to Zigbee Coordinators to trusted personnel and devices to reduce attack surface. 8. Conduct regular security assessments of IoT deployments to identify and remediate similar protocol handling weaknesses. 9. Educate operational technology teams on the implications of this vulnerability and response steps. 10. Consider fallback or redundant communication paths for critical IoT devices to maintain availability during disruptions.
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.