Is CVE-2026-12214 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-12214 being exploited in the wild.

How severe is CVE-2026-12214?

High severity, with a CVSS score of 7.8, published 15 June 2026.

Which products and versions are affected?

Qihoo 360 360 Total Security 6.0.

Is there a fix for CVE-2026-12214?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-12214 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2026-12214?

Check whether you run Qihoo 360 360 Total Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-12214: Qihoo 360 Total Security protection bypass in Nucleus Engine

CVE-2026-12214 · Severity: high · CVSS 7.8 · Published 2026-06-15

A security bypass vulnerability exists in Qihoo 360 Total Security's Nucleus Engine, a component responsible for monitoring and blocking suspicious system activities. An attacker with local access can bypass the software's protection mechanisms to create or modify malicious scheduled tasks without being detected. This could allow an attacker to maintain long-term access to a system, escalate their privileges, or deploy malware while remaining hidden from the security software.

Vendors: Qihoo 360.

Quick answers

Is CVE-2026-12214 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-12214 being exploited in the wild.
How severe is CVE-2026-12214?: High severity, with a CVSS score of 7.8, published 15 June 2026.
Which products and versions are affected?: Qihoo 360 360 Total Security 6.0.
Is there a fix for CVE-2026-12214?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-12214 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-12214?: Check whether you run Qihoo 360 360 Total Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A security feature bypass vulnerability exists in the Nucleus Engine Monitoring Logic of Qihoo 360 Total Security 6.0. The engine monitors the Windows Task Scheduler RPC interface (UUID 0A74EF1C-41A4-4E06-83AE-DC74FB1CDD53) by intercepting 'RpcStringBindingComposeW' calls. However, the detection logic only looks for explicit 'localhost' strings in the 'NetworkAddr' parameter. An attacker can bypass this by setting 'NetworkAddr' to NULL or '0', which the RPC runtime still resolves to the local host but the Nucleus Engine fails to flag. This allows for the unauthorized creation or modification of scheduled tasks via 'SchRpcRegisterTask' without triggering security alerts. The vendor has reportedly not responded to the disclosure.

Affected products

Qihoo 360 Total Security 6.0

Timeline

2026-06-15: disclosed: Public disclosure of the vulnerability and exploit code.
2026-06-15: advisory: CVE-2026-12214 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.