CVE-2025-65295: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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:HExploitation 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 2026-10-25.
What to do
AI-suggested
1. Immediate action should be taken to check for and apply any official firmware updates from Aqara that address these vulnerabilities. 2. If patches are not yet available, organizations should isolate affected devices on segmented networks with strict access controls to limit exposure. 3. Implement network-level filtering to restrict firmware update traffic to trusted sources only. 4. Monitor network traffic for unusual firmware update attempts or anomalies in device behavior. 5. Consider deploying intrusion detection systems tailored to IoT device traffic to detect exploitation attempts. 6. Engage with Aqara support to obtain timelines for patches and request security advisories. 7. For environments with high security requirements, evaluate replacing vulnerable devices with alternatives that follow secure update practices. 8. Educate users and administrators about the risks of unverified firmware updates and the importance of device hygiene. 9. Conduct regular audits of IoT device firmware versions and cryptographic configurations to ensure compliance with security policies.
Description
Multiple vulnerabilities in Aqara Hub firmware update process in the Camera Hub G3 4.1.9_0027, Hub M2 4.3.6_0027, and Hub M3 4.3.6_0025 devices, allow attackers to install malicious firmware without proper verification. The device fails to validate firmware signatures during updates, uses outdated cryptographic methods that can be exploited to forge valid signatures, and exposes information through improperly initialized memory.