Live Active security incident? Get immediate response
CVE Record

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

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.

HighCVSS 8.5Not KEV-listed Updated
Discuss exposure Back to CVEs
Glexia's Take high

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-12214 affects Qihoo 360 Total Security 6.0. A local user can reportedly bypass a protection mechanism in the Nucleus Engine component. This matters most on endpoints where untrusted users or malware already have local access. Public exploit material is referenced, but the sources do not show confirmed active exploitation.

Executive priority

Treat as a high-priority endpoint exposure if Qihoo 360 Total Security 6.0 is deployed. The issue is local, not remote, but public exploit availability and high impact make it important for environments with shared workstations, weak endpoint controls, or elevated business sensitivity.

Technical view

The flaw is reported in Nucleus Engine Monitoring Logic, involving RpcStringBindingComposeW and manipulation of the NetworkAddr argument. It is classified as CWE-693, protection mechanism failure. CVSS 4.0 is 8.5 with local attack vector, low complexity, low privileges, no user interaction, and high vulnerable-system confidentiality, integrity, and availability impact.

Likely exposure

Organizations running Qihoo 360 Total Security 6.0 on Windows endpoints are the stated exposure. Risk is higher on shared systems, unmanaged endpoints, or hosts where attackers may gain a low-privileged local foothold. The provided affected-product data does not confirm other versions.

Exploitation context

The advisory states the exploit has been released publicly and may be used for attacks. CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation. The attack requires local access and low privileges, limiting remote mass exploitation but increasing post-compromise risk.

Researcher notes

Evidence is centered on VulDB, CVE records, and a linked GitHub issue. Vendor response is reported as absent. No official patch or mitigation is named in the supplied sources. The submission reference mentions a business product context, while the affected data names Qihoo 360 Total Security 6.0.

Mitigation direction

  • Inventory endpoints for Qihoo 360 Total Security 6.0.
  • Check Qihoo 360 vendor guidance for updates or mitigations.
  • Restrict local user access on affected systems.
  • Prioritize remediation on shared, kiosk, and high-value endpoints.
  • Monitor vendor and VulDB pages for patch status changes.

Validation and detection

  • Confirm installed Qihoo 360 Total Security versions across endpoints.
  • Verify whether version 6.0 is present in production.
  • Review endpoint logs for suspicious local privilege activity.
  • Track whether public exploit indicators apply to your environment.
  • Document compensating controls where patch guidance is unavailable.
Prepared
Confidence
medium
Sources
7

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-693: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-12214 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
High
CVSS
8.5 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4 CVSS vectors
6 Timeline events
0 ADP providers
6 Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

Score Version Severity Vector Exploit Impact Source
8.5 CVSS 4.0 High 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 — — VulDB
7.8 CVSS 3.1 High CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R 1.8 5.9 VulDB
7.8 CVSS 3.0 High CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R 1.8 5.9 VulDB
6.8 CVSS 2.0 Medium AV:L/AC:L/Au:S/C:C/I:C/A:C/E:POC/RL:ND/RC:UR 3.1 10 VulDB

Vulnerability scoring details

Base CVSS 4.0 score

8.5 High
CVSS 4.0 vector shape for CVE-2026-12214 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
Qihoo 360 Total Security 6.0 Listed
Weakness

CWE details

CWE-693

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-693 · source CWE mapping

Protection Mechanism Failure

Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligence Same-CWE CVEs