# CVE-2026-121608: Qihoo 360 D603-2/D600-2/D606-6 Timezone Push iscm on_push_message os command injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-pw8g-mg6x-g4wh

## What is CVE-2026-121608?

CVE-2026-121608 is a medium-severity vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026. 

### Official description

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).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-121608?


## How do I fix CVE-2026-121608?

No fix has been published for CVE-2026-121608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121608 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121608 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121608 and fix it if it is affected.

What it is: CVE-2026-121608 is a medium-severity vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121608 exists.

Affected product: Qihoo 360 D600-2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121608/ (Markdown: https://insights.sbomify.com/CVE-2026-121608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121608
- OSV: https://osv.dev/vulnerability/CVE-2026-121608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121608/
Summaries are generated and may contain mistakes; the official description above is the record.
