{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121607 exists.","exposure":"","fix":"No fix has been published for CVE-2026-121607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-121607 is a critical vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-121607 and fix it if it is affected.\n\nWhat it is: CVE-2026-121607 is a critical vulnerability in Qihoo 360 D600-2, published on 4 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121607 exists.\n\nAffected product: Qihoo 360 D600-2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-121607/ (Markdown: https://insights.sbomify.com/CVE-2026-121607/index.md)","id":"CVE-2026-121607","markdown":"https://insights.sbomify.com/CVE-2026-121607/index.md","name":"CVE-2026-121607","record":{"aliases":["GHSA-rwrj-5289-458f"],"analysis":null,"analysis_generated_by":null,"assigner":"VulDB","cpe":[],"cvss":{"score":10,"severity":"critical","source":"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","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Qihoo 360 D603-2/D600-2/D606-6/D706 iscm testspeed_command os command injection","id":"CVE-2026-121607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Qihoo 360 D603-2/D600-2/D606-6 Timezone Push iscm on_push_message os command injection","id":"CVE-2026-121608"},"nickname":null,"packages":[],"prev":{"headline":"Qihoo 360 D621-2/D603-2/D600-2/D619/D606-6/D706 Firmware Signature Verification iscm verify_sign signature verification","id":"CVE-2026-121606"},"products":["D600-2","D603-2","D606-6","D706"],"published":"2026-11-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-09","vendors":["Qihoo 360"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-121607/"}