# CVE-2026-121606: Qihoo 360 D621-2/D603-2/D600-2/D619/D606-6/D706 Firmware Signature Verification iscm verify_sign signature verification


- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-4g7h-mgvw-cqjw

## What is CVE-2026-121606?

CVE-2026-121606 is a critical vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026. 

### Official description

A vulnerability has been found in Qihoo 360 D621-2, D603-2, D600-2, D619, D606-6 and D706 up to 6.4.9. Affected by this issue is the function verify_sign of the file fs2/bin/iscm of the component Firmware Signature Verification. Such manipulation of the argument sign leads to improper verification of cryptographic signature. The attack can be launched remotely. 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.

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

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


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

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

## Is CVE-2026-121606 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121606 is a critical vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121606 exists.

Affected product: Qihoo 360 D600-2. 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-121606/ (Markdown: https://insights.sbomify.com/CVE-2026-121606/index.md)
```

## Sources

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

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