CVE-2026-121606
CVE-2026-121606 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.
Key facts
- Severity: Critical (CVSS 3.x base score 10.0)
- CVSS v2: 10.0
- CVSS v4: 9.3
- EPSS exploit prediction: 0% (15th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-345
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-121606?
- 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.
- How severe is CVE-2026-121606?
- CVE-2026-121606 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-121606 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-121606?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2026-121606 published?
- CVE-2026-121606 was published on 2026-11-04 and last updated on 2026-11-09.
References
- https://gist.github.com/gajgdm6-cpu/cf98af20ddb77f27a7c112214a6280f7
- https://vuldb.com/cve/CVE-2026-121606
- https://vuldb.com/submit/1023261
- https://vuldb.com/vuln/430443
- https://vuldb.com/vuln/430443/cti
Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities
- CVE-2026-62874 — Critical (CVSS 10.0): Insufficient verification of data authenticity in Azure Billing allows an unauthorized attacker to elevate privileges…
- CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
- CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
- CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
- CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
- CVE-2026-104056 — Critical (CVSS 9.8): Authlib version 1.7.2 and below contains a vulnerability where discovery JSON metadata is cached without validation or…
Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →