CVE-2026-121608Qihoo 360 D603-2 command injection
CVE-2026-121608 is a command injection in Qihoo 360 D603-2, rated medium (5.5 on CVSS 4.0).
Why this priority: A public proof of concept exists and exploitation can be automated.
Published · Updated · NVD status: Deferred
What it is
Input ends up inside a command the software runs, so an attacker can add commands of their own. Input reaches an operating-system command line, letting an attacker run their own commands on the host.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service.
Is it being exploited?
CISA's SSVC assessment notes a public proof of concept. It can be exploited automatically, at scale. EPSS estimates a 1.3% chance of exploitation activity in the next 30 days, higher than 71% of scored CVEs.
What to do
- Upgrade Qihoo 360 D603-2 to 6.4.0 or later. Other affected products have their own fixed versions on this page.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
A vulnerability was determined in Qihoo 360 D603-2, D600-2 and D606-6 up to 6.3.2. This vulnerability affects the function on_push_message of the file /fs2/bin/iscm of the component Timezone Push Handler. Executing a manipulation of the argument tz can lead to os command injection. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 6.4.0 is able to resolve this issue. Upgrading the affected component is advised. Firmware 6.4.0 gates the path with a new check_timezone_parameter validation (verified by VulDB vulnerability analysis team via disassembly).
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
- Template engines. The flaw sits between untrusted input and code or command execution.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.
Questions to answer about your own systems
- Where does Qihoo 360 D603-2 run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.