VulnerabilityPublished 8 Aug 2025

CVE-2025-8393: Dreame Technology Dreamehome iOS app · CWE-295

Affects Dreame Technology Dreamehome iOS appSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.3High

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 8 Aug 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

Affected software

Product	Affected	Fixed in
Dreame Technology Dreamehome iOS app	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations and users should immediately avoid connecting the Dreamehome iOS app over untrusted or public networks until a patch is released. Network segmentation and use of VPNs can reduce exposure by encrypting traffic and isolating device management communications. Users should verify that the app is updated to the latest version once Dreame Technology releases a fix that enforces strict certificate validation, rejecting self-signed or untrusted certificates. Organizations should conduct network monitoring to detect unusual TLS handshake patterns or unexpected certificate acceptance. Additionally, implementing multi-factor authentication (MFA) for the Dreamehome app or associated accounts can reduce the impact of credential compromise. Security teams should engage with Dreame Technology to obtain timelines for patches and request security advisories. If possible, temporarily disable remote management features or restrict device control to trusted networks only. Finally, educating users about the risks of connecting to untrusted Wi-Fi networks and encouraging the use of secure connections will help reduce the likelihood of successful MITM attacks.

Description

A TLS vulnerability exists in the phone application used to manage a connected device. The phone application accepts self-signed certificates when establishing TLS communication which may result in man-in-the-middle attacks on untrusted networks. Captured communications may include user credentials and sensitive session tokens.

Impact

For European organizations using Dreame Technology's Dreamehome iOS app to manage smart devices, this vulnerability poses a substantial risk. The exposure of user credentials and session tokens through MITM attacks can lead to unauthorized access to connected devices, potentially allowing attackers to control or disrupt device functionality. This could compromise privacy and security, especially in environments where smart devices control critical home or office functions. The risk is heightened in public or semi-public network environments common in urban European settings, such as cafes, airports, or corporate guest networks, where attackers can easily position themselves on the same network segment. Additionally, compromised credentials could be leveraged for lateral movement within corporate networks if devices are integrated into broader IoT or enterprise systems. The confidentiality and integrity breaches could result in data leakage, unauthorized device manipulation, and erosion of user trust. Given the increasing adoption of smart home and IoT devices across Europe, the vulnerability could have widespread implications if exploited at scale.

CWE-295Improper Certificate Validation (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not validate, or incorrectly validates, a certificate.
Architecture and Design · Implementation
Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
Implementation
If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V9.2.1 (opens in a new tab)
V1.9.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Aug 2025, 16:47 UTC

WeaknessesCWE-295

Technical details

References

Community reviews

Related threats