CVE-2025-65297
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAqara Hub devices including Camera Hub G3 4.1.9_0027, Hub M2 4.3.6_0027, and Hub M3 4.3.6_0025 automatically collect and upload unencrypted sensitive information. Note that this occurs without disclosure or consent from the manufacturer.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAqara smart home hub devices (Camera Hub G3, Hub M2, Hub M3) automatically collect and transmit sensitive user data to external servers without encryption. This privacy-focused vulnerability allows intercepted network traffic to expose personal information, home automation patterns, and device usage data due to the lack of transport-layer security during upload.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.3.6_0027= 4.3.6_0025= 4.1.9_0027CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Aqara hub modelLocate the device label or check the Aqara app for the device model name (Camera Hub G3, Hub M2, or Hub M3)Affected if The device is not one of these three models - only Camera Hub G3, Hub M2, or Hub M3 are affected
-
Check the installed firmware versionAccess the device settings through the Aqara app or web interface, or check the device management page to view the firmware version numberAffected if The firmware version is exactly 4.3.6_0027 for Hub M2, 4.3.6_0025 for Hub M3, or 4.1.9_0027 for Camera Hub G3 (exact version match)
-
Inspect outbound network traffic for unencrypted dataUse a network packet capture tool (such as Wireshark or tcpdump) on network traffic originating from the hub device, looking for plaintext HTTP traffic sending sensitive data to external IP addressesAffected if Plaintext HTTP traffic containing personal data, home automation patterns, or device usage information is transmitted to external servers without TLS encryption
-
Verify if sensitive data is sent to external serversMonitor the hub's outbound connections using a network firewall or monitoring tool to identify external server communications; examine packet contents for unencrypted transmission of user dataAffected if The hub transmits sensitive user information (personal data, automation patterns, device usage) to external servers using unencrypted protocols
A user is affected if they own a Camera Hub G3, Hub M2, or Hub M3 with one of the specific firmware versions listed and the device transmits sensitive data to external servers without encryption.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate affected hubs on a separate VLAN or network segment to limit exposure; contact Aqara for a firmware update that implements encryption and provides transparency about data collection; monitor outbound traffic for suspicious data exfiltration patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65297 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65297 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data