Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-121607

Qihoo 360 D603-2/D600-2/D606-6/D706 iscm testspeed_command os command injection

Products / packages Qihoo 360 D603-2 · Qihoo 360 D600-2 · Qihoo 360 D606-6 · 1 more

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 05/11/2026, 02:25:33 UTC
VulDB · CVSS:4.0 · 10
Assessment vectorCVSS: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
VulDB · CVSS:3.1 · 10
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C
VulDB · CVSS:3.0 · 10
Assessment vectorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C
VulDB · CVSS 2 / source score · 10
Assessment vectorAV:N/AC:L/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:C
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

critical10.0

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Exploit reference published

Source-linked evidence; not proof of attacks in the wild or independent validation.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

Qihoo 360 devices D603-2, D600-2, D606-6, and D706 up to version 6.4.9 have an os command injection vulnerability in the testspeed_command function. The attack may be initiated remotely by manipulating the host argument.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Qihoo 360 · VulDB

D603-2

10 ranges
VulDB version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

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

unaffected

unknown

Other versions: unknown

Product identifiers (CPE)cpe:2.3:a:qihoo_360:d603-2:*:*:*:*:*:*:*:*

Qihoo 360 · VulDB

D600-2

10 ranges
VulDB version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

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

unaffected

unknown

Other versions: unknown

Product identifiers (CPE)cpe:2.3:a:qihoo_360:d600-2:*:*:*:*:*:*:*:*

Qihoo 360 · VulDB

D606-6

10 ranges
VulDB version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

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

unaffected

unknown

Other versions: unknown

Product identifiers (CPE)cpe:2.3:a:qihoo_360:d606-6:*:*:*:*:*:*:*:*

Qihoo 360 · VulDB

D706

10 ranges
VulDB version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

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

unaffected

unknown

Other versions: unknown

Product identifiers (CPE)cpe:2.3:a:qihoo_360:d706:*:*:*:*:*:*:*:*
Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.

gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a ↗Attributed to VulDB

Original source description

Read the full publisher 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.

References

5 sources
VulDB · advisory #430444
Security advisoryVulDB
VulDB · threat intelligence #430444
Security advisoryVulDB
VulDB · CVE-2026-121607
Security advisoryVulDB
VulDB · submission #1023262
Source referenceVulDB
gist.github.com/gajgdm6-cpu/e8ef7f512bebb987b0119562873afd5a
Public exploit referenceVulDB

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-121607

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-78 ↗

OS Command Injection

VulDB

Related →
CWE-77 ↗

Command Injection

VulDB

Related →
Contributing organizations · 1
VulDB

Assigning organization

2026-11-04

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.