VulnerabilityPublished 3 Feb 2026Updated 23 Feb 2026

CVE-2026-1803: Ziroom ZHOME A0101 · Use of Default Credentials

Affects Ziroom ZHOME A0101Source CVE Database V5

Public exploit available · CVSS 9.2 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

9.2Critical

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system 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 vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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
ZiroomZHOME A0101	Affected =1.0.1.0	Fixed in–

AI-suggested

Since no official patches or updates are currently available from the vendor, organizations should implement the following specific mitigations: 1) Immediately change any default credentials on the Dropbear SSH service if possible, or disable SSH access entirely if not required. 2) Restrict network access to the affected devices by implementing strict firewall rules that limit SSH access to trusted IP addresses or internal networks only. 3) Employ network segmentation to isolate smart home devices from critical business or personal networks to reduce lateral movement risks. 4) Monitor network traffic for unusual SSH connection attempts or brute-force activities targeting these devices. 5) Use intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts based on known exploit signatures. 6) Consider deploying virtual private networks (VPNs) or zero-trust network access (ZTNA) solutions to control remote access securely. 7) Maintain an inventory of all Ziroom ZHOME A0101 devices and plan for device replacement or firmware updates once patches become available. 8) Educate users about the risks of default credentials and the importance of changing them. These targeted actions go beyond generic advice by focusing on network controls, monitoring, and access restrictions specific to the affected component and device context.

Description

A weakness has been identified in Ziroom ZHOME A0101 1.0.1.0. Impacted is an unknown function of the component Dropbear SSH Service. This manipulation causes use of default credentials. Remote exploitation of the attack is possible. The complexity of an attack is rather high. The exploitability is considered difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The impact of CVE-2026-1803 is significant for organizations and individuals using Ziroom ZHOME A0101 devices. Unauthorized remote access via default credentials can lead to full compromise of the device, exposing sensitive personal or organizational data managed by the smart home system. Attackers could manipulate device configurations, disable security controls, or use the device as a foothold for lateral movement within a network. This could result in privacy violations, service disruptions, and potential escalation to other connected systems. Given the device's role in smart home automation, critical infrastructure such as security cameras, door locks, or environmental controls could be compromised, posing physical security risks. The absence of vendor response and patches increases the risk window, forcing users to rely on network-level protections. Organizations deploying these devices in corporate or residential environments face reputational damage, operational interruptions, and potential regulatory compliance issues if breaches occur. The high CVSS score underscores the urgency of addressing this vulnerability to prevent exploitation.

Summary

CVE-2026-1803 identifies a critical security vulnerability in the Ziroom ZHOME A0101 smart home device, specifically version 1.0.1.0. The issue arises from the use of default credentials within the Dropbear SSH service component, which is a lightweight SSH server commonly embedded in IoT and network devices. This default credential usage allows remote attackers to authenticate without valid credentials, potentially gaining unauthorized access to the device. The vulnerability does not require user interaction or prior authentication, and the attack vector is network-based, meaning an attacker can exploit it remotely over the internet or local network. However, the attack complexity is rated high, indicating that exploitation requires significant skill or conditions. The vulnerability impacts confidentiality, integrity, and availability, as attackers could access sensitive data, modify device settings, or disrupt device operations. Despite public availability of exploit code, no confirmed active exploitation has been reported. The vendor, Ziroom, has not responded to vulnerability disclosure requests, and no official patches or updates have been released. This leaves affected devices exposed and necessitates alternative mitigation strategies. The CVSS 4.0 base score of 9.2 reflects the critical nature of the vulnerability, with network attack vector, no privileges or user interaction required, and high impacts on all security objectives. The lack of scope change indicates the vulnerability is contained within the affected component but still severe due to the device's role in smart home environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:57 UTC

Technical details

References

Community reviews

Related threats