External risk intelligence

Qihoo 360 Firmware Signature Verification Vulnerability Allows Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-121606

The affected products are Qihoo 360 routers/network devices. These devices are commonly deployed as internet-facing gateways and edge services. While the specific function is firmware signature verification, vulnerabilities in such components on internet-exposed gateway devices are frequently reachable via network-facing interfaces or during remote update processes, making public internet exposure common for this product class.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the firmware signature verification function of certain Qihoo 360 devices allows for remote attacks. The issue stems from improper cryptographic signature verification, and exploit code has been publicly disclosed. The vendor has not responded to inquiries regarding this matter.

  • Flaw bypasses security checks on device updates.
  • Critical routers remotely exploitable, vendor unresponsive.
  • Confirm device relevance; assess exposure and impact.

Attack Path

How an attacker could exploit the issue

An attacker can remotely reach the vulnerable firmware signature verification function on Qihoo 360 devices by manipulating the `sign` argument. This improper signature verification can lead to significant compromise when exploited.

  • No authentication or special access needed.
  • Triggered by manipulating the `sign` argument.
  • Allows critical system compromise.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, the firmware signature verification process could be improperly manipulated, potentially affecting the integrity of the device's firmware.

  • Device firmware integrity at risk.
  • Remote manipulation of signature verification.
  • Unauthorized firmware modifications possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

The affected devices are network-facing gateways, suggesting that infrastructure and network security teams are likely responsible for managing this vulnerability. The first practical step is to identify all instances of the affected Qihoo 360 devices, determine their exposure to the internet, and ascertain their business criticality. Once these factors are understood, the accountable owner can be identified to plan remediation based on the assessed risk.

  • Identify device inventory and exposure.
  • Verify business criticality and impact.
  • Plan remediation with vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Qihoo 360 equipment affected by CVE-2026-121606?

These products are networking devices, specifically routers often used to manage internet traffic and provide gateway connectivity for homes or small offices. They handle critical tasks like routing data packets and managing device firmware updates to maintain system stability and security.

How does this vulnerability impact firmware signature verification?

This issue is categorized under improper verification of cryptographic signatures (CWE-345 and CWE-347). Essentially, the device fails to correctly validate the authenticity of digital signatures during certain processes. Because the system does not properly confirm that the incoming data or firmware update is legitimate, an attacker can manipulate the process to bypass security controls.

Do I need special access to trigger this vulnerability?

No. The flaw exists within the verify_sign function, which can be reached remotely. An attacker can trigger the issue by manipulating the 'sign' argument directly, without requiring prior authentication or user interaction. Note that internal operations not interacting with this specific signing function or argument are not the mechanism for this trigger.

How does Halo Surface Signal characterize the risk for these devices?

Halo Surface Signal identifies these routers as typically deployed in internet-facing roles, such as edge gateways. Because these devices sit at the perimeter of a network to manage traffic, their exposure to the public internet makes them prime targets for remote probes and unauthorized access attempts aimed at this specific verification flaw.

What is the first step for owners of these Qihoo 360 devices?

The priority is to locate all units in your environment and determine if they are exposed to the internet. Since the vendor has not provided a resolution, you should assess the business criticality of these gateways and isolate them from public access where possible to limit the risk of remote manipulation until further guidance is available.

References