VulnerabilityPublished 10 Dec 2025Updated 11 Dec 2025

CVE-2025-65297: J2EE Misconfiguration: Data Transmission Without Encryption

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Network Segmentation: Isolate Aqara Hub devices on separate VLANs or network segments to limit exposure to sensitive internal networks.
Enforce Network Encryption: Use VPNs or secure tunnels for all IoT device traffic to prevent interception of unencrypted data.
Monitor Network Traffic: Deploy IDS/IPS solutions to detect unusual data transmissions from Aqara devices, focusing on unencrypted uploads.
Disable Unnecessary Features: Where possible, disable automatic data collection or cloud upload features on affected devices.
Device Inventory and Risk Assessment: Identify all Aqara devices in the environment and assess their usage and data sensitivity.
Engage with Manufacturer: Request official patches or firmware updates addressing the vulnerability and demand transparency regarding data collection.
User Awareness: Inform users about the privacy risks and advise on safe usage practices, including avoiding these devices in sensitive environments.
Regulatory Compliance Review: Evaluate the impact of this vulnerability on GDPR and other privacy regulations, and prepare for potential reporting obligations.
Consider Alternative Devices: For critical environments, replace vulnerable Aqara devices with alternatives that ensure encrypted data transmission and user consent.
Apply Network Access Controls: Restrict device communication to only necessary endpoints and block unauthorized external connections.

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 automatically collect and upload unencrypted sensitive information. Note that this occurs without disclosure or consent from the manufacturer.

Impact

For European organizations, the primary impact is the exposure of sensitive information transmitted by Aqara Hub devices, which can include personal data, network information, or other confidential details. This exposure can lead to privacy violations, regulatory non-compliance (notably GDPR), and potential reputational damage. Organizations using these devices in office environments or employee residences for remote work may inadvertently expose internal network details or user data. The unencrypted transmission allows attackers with network access to perform passive eavesdropping attacks, potentially leading to targeted phishing or further exploitation. While the vulnerability does not directly compromise device integrity or availability, the confidentiality breach alone is significant, especially for sectors handling sensitive data such as finance, healthcare, and government. The lack of manufacturer disclosure and consent complicates risk management and incident response. Additionally, the presence of these devices in smart buildings or IoT-integrated infrastructures could provide attackers with reconnaissance information for broader attacks.

CWE-5J2EE Misconfiguration: Data Transmission Without Encryption (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted.
System Configuration
The product configuration should ensure that SSL or an encryption mechanism of equivalent strength and vetted reputation is used for all access-controlled pages.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/Chapoly1305/myCVEReports/blob/main/Aqara/Unauthorized-Data-Upload.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 17 Dec 2025, 23:14 UTC

WeaknessesCWE-5

Technical details

References

Community reviews

Related threats