VulnerabilityPublished 20 Mar 2026

CVE-2026-4476: Yi Technology YI Home Camera · Missing Authentication

Affects Yi Technology YI Home CameraSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 4.0 base score

5.3Medium

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

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

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

Base metrics

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
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: Adjacent: The vulnerable system is bound to a protocol 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 proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
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 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 31 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
Yi TechnologyYI Home Camera	Affected =2 2.1.1_20171024151200	Fixed in–

AI-suggested

Given the absence of an official patch or vendor response, organizations should implement several practical mitigations: 1) Isolate Yi Home Cameras on dedicated VLANs or separate network segments to restrict access only to authorized devices and users. 2) Employ network access controls such as MAC filtering and strong Wi-Fi encryption to limit local network access. 3) Disable remote access features if enabled, to reduce exposure. 4) Monitor network traffic for unusual activity related to the camera's IP or MAC addresses, including unexpected CGI endpoint requests. 5) Consider replacing affected devices with models from vendors that provide timely security updates and support. 6) If possible, update to a newer firmware version if available, or apply community-developed patches after thorough testing. 7) Educate users about the risks of connecting IoT devices to unsecured or public networks. 8) Use network intrusion detection systems (NIDS) to detect exploitation attempts targeting the CGI endpoint. These steps go beyond generic advice by focusing on network segmentation, monitoring, and device replacement strategies tailored to the vulnerability's characteristics.

Description

CVE-2026-4476 is a medium-severity vulnerability affecting Yi Technology YI Home Camera version 2 2.1.1_20171024151200. The flaw involves a missing authentication check in a CGI endpoint within the device's web interface, allowing unauthorized access to certain functions. Exploitation requires access to the local network, and no user interaction or prior authentication is needed. Although the vendor was notified, no patch or response has been issued. The vulnerability could allow attackers on the same network to manipulate the camera or access sensitive functions, potentially compromising device confidentiality and integrity. The CVSS 4.0 score is 5.3, reflecting moderate impact and ease of exploitation within a local network.

Impact

The primary impact of CVE-2026-4476 is unauthorized access to the Yi Home Camera's functions without authentication, which can lead to privacy violations and potential manipulation of the device. Attackers on the same local network could exploit this flaw to view live video feeds, alter camera settings, or use the device as a pivot point for further attacks within the network. This compromises confidentiality and integrity of the device and its data. Although the vulnerability does not directly affect availability, misuse could disrupt normal camera operations. For organizations, especially those using these cameras in sensitive environments such as offices, healthcare, or critical infrastructure, this vulnerability poses a significant privacy and security risk. The lack of vendor response and patch increases the window of exposure, potentially enabling attackers to develop and deploy exploits. The requirement for local network access limits the scope somewhat but does not eliminate risk, as many IoT devices are deployed in environments with multiple users or insufficient network segmentation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:43 UTC

Technical details

References

Community reviews

Related threats