CVE-2025-65291: Aqara Hub devices including Hub M2 · Improper Certificate Validation
Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Dec 2025
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 26 Oct 2026.
What to do
AI-suggested
- Immediately isolate Aqara Hub devices on dedicated VLANs or network segments with strict access controls to limit exposure to untrusted networks.
- Disable any remote or cloud-based access features until patches or firmware updates are available.
- Monitor network traffic for unusual TLS handshake failures or unexpected CoAP communications that may indicate MitM attempts.
- Engage with Aqara or device vendors to obtain firmware updates that properly validate TLS certificates and apply them promptly.
- Implement network-level TLS inspection and certificate pinning where feasible to detect and block invalid certificates.
- Educate users and administrators about the risks of connecting these devices to public or unsecured Wi-Fi networks.
- Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalies in IoT device communications.
- Maintain an inventory of all Aqara devices and their firmware versions to track vulnerable assets effectively.
Description
Aqara Hub devices including Hub M2 4.3.6_0027, Hub M3 4.3.6_0025, Camera Hub G3 4.1.9_0027 fail to validate server certificates in TLS connections for discovery services and CoAP gateway communications, enabling man-in-the-middle attacks on device control and monitoring.