# CVE-2026-4478: Yi Technology YI Home Camera HTTP Firmware Update ipc signature verification

> Attackers can bypass firmware signature verification to install malicious firmware on Yi Home Cameras, potentially gaining remote code execution.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-mp64-rm5r-c35p

## What is CVE-2026-4478?

CVE-2026-4478 is a critical vulnerability in YI Home Camera, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in Yi Technology YI Home Camera 2 2.1.1_20171024151200. This impacts an unknown function of the file home/web/ipc of the component HTTP Firmware Update Handler. The manipulation leads to improper verification of cryptographic signature. The attack is possible to be carried out remotely. The complexity of an attack is rather high. The exploitability is said to be difficult. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-4478?


## How do I fix CVE-2026-4478?

No fix has been published for CVE-2026-4478 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4478 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4478 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4478 and fix it if it is affected.

What it is: CVE-2026-4478 is a critical vulnerability in YI Home Camera, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4478 exists.

Affected product: YI Home Camera. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4478/ (Markdown: https://insights.sbomify.com/CVE-2026-4478/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4478
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4478
- OSV: https://osv.dev/vulnerability/CVE-2026-4478

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4478/
Summaries are generated and may contain mistakes; the official description above is the record.