# CVE-2026-12214: Qihoo 360 Total Security Nucleus Engine Monitoring Logic RpcStringBindingComposeW protection mechanism

> Local attackers can bypass the Nucleus Engine Monitoring Logic protection mechanism in Qihoo 360 Total Security by manipulating network address arguments.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-9r2r-c24c-x9g4

## What is CVE-2026-12214?

CVE-2026-12214 is a high-severity vulnerability in Qihoo 360 Total Security, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in Qihoo 360 Total Security 6.0. This vulnerability affects the function RpcStringBindingComposeW of the component Nucleus Engine Monitoring Logic. Performing a manipulation of the argument NetworkAddr results in protection mechanism failure. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2026-12214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12214 is a high-severity vulnerability in Qihoo 360 Total Security, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12214 exists.

Affected product: Qihoo 360 Total Security. 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-12214/ (Markdown: https://insights.sbomify.com/CVE-2026-12214/index.md)
```

## Sources

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

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