CVE-2026-4475
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 · uneditedA vulnerability has been found in Yi Technology YI Home Camera 2 2.1.1_20171024151200. The affected element is an unknown function of the file home/web/ipc. Such manipulation leads to hard-coded credentials. Access to the local network is required for this attack to succeed. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceThe YI Home Camera 2 (firmware version 2.1.1_20171024151200) contains hard-coded credentials embedded in an unknown function within the home/web/ipc file. An attacker with local network access can leverage these credentials to gain unauthorized access to the camera system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 device modelCheck if the device is a YI Home Camera 2 by reviewing the device label, web interface, or mobile app device informationAffected if Device is not a YI Home Camera 2 then it is not affected by this specific CVE
-
Check the installed firmware versionAccess the camera's web interface or mobile app settings to view the firmware version, or check the device label for version informationAffected if Firmware version is 2.1.1_20171024151200 exactly, or appears to be a variant of the 2.1.1_20171024 baseline firmware build
-
Access the home/web/ipc fileIf you have shell access or can extract the firmware, navigate to the home/web/ipc file and inspect its contents for embedded credentialsAffected if The file contains hard-coded usernames or passwords that are not user-configurable or unique to each device
-
Verify network accessibilityConfirm the camera is reachable from your local network and check if it exposes services that accept the hard-coded credentialsAffected if The camera is accessible on the local network without isolation
You are affected if you have a YI Home Camera 2 running firmware version 2.1.1_20171024151200 with hard-coded credentials present in the home/web/ipc file accessible from your local network.
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 dataSince the vendor did not respond and no patch is available, implement network segmentation to isolate the camera on a restricted VLAN, apply firewall rules to limit access, monitor for unauthorized access attempts, and consider replacing the device if security updates are unavailable.
- Consultation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4475 — 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-2026-4475 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