cve.bz

CVE-2026-121606

9.3 critical

Critical (9.3).

On this page
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.

Severity

CVSS 4.0

9.3 critical
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

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-347 Improper Verification of Cryptographic Signature
Published
Modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-121606 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121606?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121606?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121606 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
Qihoo 360 D621-26.4.0
Qihoo 360 D621-26.4.1
Qihoo 360 D621-26.4.2
Qihoo 360 D621-26.4.3
Qihoo 360 D621-26.4.4
Qihoo 360 D621-26.4.5
Qihoo 360 D621-26.4.6
Qihoo 360 D621-26.4.7
Qihoo 360 D621-26.4.8
Qihoo 360 D621-26.4.9
Qihoo 360 D603-26.4.0
Qihoo 360 D603-26.4.1
Qihoo 360 D603-26.4.2
Qihoo 360 D603-26.4.3
Qihoo 360 D603-26.4.4
Qihoo 360 D603-26.4.5
Qihoo 360 D603-26.4.6
Qihoo 360 D603-26.4.7
Qihoo 360 D603-26.4.8
Qihoo 360 D603-26.4.9
Qihoo 360 D600-26.4.0
Qihoo 360 D600-26.4.1
Qihoo 360 D600-26.4.2
Qihoo 360 D600-26.4.3
Qihoo 360 D600-26.4.4
Qihoo 360 D600-26.4.5
Qihoo 360 D600-26.4.6
Qihoo 360 D600-26.4.7
Qihoo 360 D600-26.4.8
Qihoo 360 D600-26.4.9
Qihoo 360 D6196.4.0
Qihoo 360 D6196.4.1
Qihoo 360 D6196.4.2
Qihoo 360 D6196.4.3
Qihoo 360 D6196.4.4
Qihoo 360 D6196.4.5
Qihoo 360 D6196.4.6
Qihoo 360 D6196.4.7
Qihoo 360 D6196.4.8
Qihoo 360 D6196.4.9
Qihoo 360 D606-66.4.0
Qihoo 360 D606-66.4.1
Qihoo 360 D606-66.4.2
Qihoo 360 D606-66.4.3
Qihoo 360 D606-66.4.4
Qihoo 360 D606-66.4.5
Qihoo 360 D606-66.4.6
Qihoo 360 D606-66.4.7
Qihoo 360 D606-66.4.8
Qihoo 360 D606-66.4.9
Qihoo 360 D7066.4.0
Qihoo 360 D7066.4.1
Qihoo 360 D7066.4.2
Qihoo 360 D7066.4.3
Qihoo 360 D7066.4.4
Qihoo 360 D7066.4.5
Qihoo 360 D7066.4.6
Qihoo 360 D7066.4.7
Qihoo 360 D7066.4.8
Qihoo 360 D7066.4.9

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON