Qihoo 360 D621-2/D603-2/D600-2/D619/D606-6/D706 up to 6.4.9 Firmware Signature Verification fs2/bin/iscm verify_sign signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $0-$5k | 2.41- |
Summary
A vulnerability classified as very critical has been found in Qihoo 360 D621-2, D603-2, D600-2, D619, D606-6 and D706 up to 6.4.9. This affects the function verify_sign of the file fs2/bin/iscm of the component Firmware Signature Verification. Performing a manipulation of the argument sign results in signature verification.
This vulnerability was named CVE-2026-121606. The attack may be initiated remotely. In addition, an exploit is available.
The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability classified as very critical has been found in Qihoo 360 D621-2, D603-2, D600-2, D619, D606-6 and D706 up to 6.4.9. This affects the function verify_sign of the file fs2/bin/iscm of the component Firmware Signature Verification. The manipulation of the argument sign with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability.
It is possible to read the advisory at gist.github.com. This vulnerability is uniquely identified as CVE-2026-121606. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/03/2026).
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/03/2026 Advisory disclosed11/03/2026 VulDB entry created
11/03/2026 VulDB entry last update
Sources
Advisory: gist.github.comStatus: Confirmed
CNA: VulDB
CVE: CVE-2026-121606 (🔒)
GCVE (CVE): GCVE-0-2026-121606
GCVE (VulDB): GCVE-100-430443
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/03/2026 17:28Changes: 11/03/2026 17:28 (58)
Complete: 🔍
Submitter: xiaomao
Cache ID: 216::103
Submit
Accepted
- Submit #1023261: 360 (Qihoo 360) 360 Smart Camera (IPC) 6.0.24 ~ 6.4.9 Improper Verification of Cryptographic Signature (by xiaomao)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.