VulnTideExploited vulnerabilities, by vendor. Data as of .
Not in CISA KEVPublished CVSS 10.0 criticalEPSS 0.2% probability of exploitation in 30 days
Qihoo 360

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

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of . If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?
0.2%

EPSS score, percentile 15.2 of all scored records. A probability estimated by FIRST, not a report of exploitation.

CISA's SSVC assessment in the CVE record lists exploitation as poc.

How severe?
10.0 Critical

CVSS v4.0 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check Qihoo 360's advisories.

A public exploit is linked in the references.

Which versions are affected?

Affected

  • 6.4.0
  • 6.4.1
  • 6.4.2
  • 6.4.3
  • 6.4.4
  • 6.4.5

and 54 more in the table below

Versions by product

Source: CISA KEV 2026.11.10, as of ; FIRST EPSS, as of ; CVE List, as of . About the data.

Description

Qihoo 360 D621-2/D603-2/D600-2/D619/D606-6/D706 Firmware Signature Verification iscm verify_sign signature verification

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.

Source: CVE List, as of . About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check Qihoo 360's own security advisories for a fix, and compare your version with the affected versions below.

A public exploit is linked in the references.

This summary is based on the CVE record as of . Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Versions by product, as listed in the CVE record (6 products)
Qihoo 360 D621-2
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9
Qihoo 360 D603-2
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9
Qihoo 360 D600-2
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9
Qihoo 360 D619
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9
Qihoo 360 D606-6
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9
Qihoo 360 D706
StatusVersions
Affected6.4.0
Affected6.4.1
Affected6.4.2
Affected6.4.3
Affected6.4.4
Affected6.4.5
Affected6.4.6
Affected6.4.7
Affected6.4.8
Affected6.4.9

Source: CVE List, as of . About the data.

Weakness

CWE-347, CWE-345

CWE and CAPEC are maintained by MITRE; the entries are those named in the CVE record.

Timeline

DateEvent
CVE record published
CVE record last updated

References

5