CVE-2025-65290: Improper Certificate Validation
Source CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 26 Oct 2026, 10:12 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 segment Aqara Hub devices on isolated network segments with strict firewall rules to limit exposure to untrusted networks.
- Monitor network traffic for unusual patterns during firmware update windows, including unexpected TLS certificate anomalies or connections to unrecognized servers.
- Disable automatic firmware updates if possible until a vendor patch is released.
- Engage with Aqara or the device vendor to obtain security patches or firmware updates that properly validate server certificates.
- Employ network-level TLS interception detection tools to identify MitM attempts.
- For organizations deploying these devices at scale, implement device inventory and vulnerability management to track affected versions and ensure timely remediation.
- Educate IT and security teams about the risks of firmware tampering and the importance of verifying update authenticity.
- Consider deploying network intrusion detection/prevention systems (IDS/IPS) with IoT-specific signatures to detect exploitation attempts.
Description
Aqara Hub devices including Camera Hub G3 4.1.9_0027, Hub M2 4.3.6_0027, and Hub M3 4.3.6_0025 fail to validate server certificates during HTTPS firmware downloads, allowing man-in-the-middle attackers to intercept firmware update traffic and potentially serve modified firmware files.