CVE-2026-94403
Executive Summary
CVE-2026-94403 is an untrusted pointer dereference (CWE-822) vulnerability in ColorFul iGameCenter version 1.0.3.4, affecting the IOCTL handler within the ene.sys kernel driver, specifically the function sub_140001AF0. The CVE carries a CVSS 3.1 base score of 8.8, as the vulnerability requires local access and low privileges but enables a sandbox escape, permitting a local attacker to escalate privileges and execute arbitrary code in the kernel context. The vendor was contacted but did not respond, and no patch is available; public exploit code has been released, making this a high-priority risk for systems with the affected driver installed.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
Technical Analysis
The vulnerability resides in ene.sys, a kernel-mode driver that is part of the ColorFul iGameCenter software suite. The driver exposes an IOCTL (Input/Output Control) interface, which is the primary attack surface. The specific weakness is an untrusted pointer dereference (CWE-822) in the function sub_140001AF0. This class of vulnerability occurs when a kernel driver accepts a pointer value from a user-mode caller without properly validating that the pointer refers to a legitimate, accessible kernel address. A local attacker can craft a malicious IOCTL request that supplies an arbitrary pointer value. When the driver dereferences this untrusted pointer, it can be tricked into reading from or writing to an attacker-controlled memory address. Because the dereference happens in kernel mode, this can lead to arbitrary kernel memory read/write, which is the foundation for privilege escalation and code execution with ring-0 privileges.
The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) indicates that the attack is local, requires low complexity, requires low privileges, and no user interaction. The scope is changed (S:C), meaning the exploitation can impact resources beyond the vulnerable component, such as the entire operating system. The confidentiality, integrity, and availability impacts are all high. The vulnerable component is the ene.sys driver, which is likely installed as part of the iGameCenter utility used for controlling RGB lighting, fan speeds, and other hardware features on ColorFul iGame (also known as iGame) branded graphics cards and motherboards. The driver is loaded at system startup and runs with high privileges, making it a valuable target for attackers seeking to elevate from a standard user to SYSTEM.
Exploitation Scenarios
The exploitation of CVE-2026-94403 follows a typical local privilege escalation chain for vulnerable kernel drivers.
Reconnaissance and Target Identification: An attacker first gains a foothold on the target system, either through a phishing campaign, a malicious download, or another initial access vector. The attacker identifies the presence of the
ene.sysdriver by enumerating loaded drivers, checking for the iGameCenter installation, or searching for the specific driver file. The driver is typically installed inC:\Windows\System32\drivers\ene.sysor a similar location.Triggering the Vulnerability: The attacker writes a user-mode application that opens a handle to the vulnerable driver device (e.g.,
\\.\EneIoor a similar symbolic link) and sends a crafted IOCTL request. The request specifies the IOCTL code that reaches the vulnerable functionsub_140001AF0. The attacker includes a pointer value in the input buffer that points to a memory address of their choosing—often a user-mode address that they control or a kernel address they wish to read from or write to. Because the driver fails to validate the pointer, it dereferences it directly.Payload Execution and Exploitation: By manipulating the pointer, the attacker can cause the driver to read from or write to arbitrary kernel memory. A common technique is to use the arbitrary write to overwrite a kernel function pointer, such as a callback in the
_EPROCESSstructure or a pointer in theHalDispatchTable, with the address of a user-mode payload. The attacker then triggers the overwritten pointer, causing the kernel to execute their shellcode with SYSTEM privileges. Alternatively, the arbitrary read can be used to leak kernel addresses to bypass KASLR, followed by an arbitrary write to disable security mitigations. The public exploit for this CVE likely implements such a chain. No specific payload details are available from the NVD description, but the vulnerability class and the mention of a public exploit strongly suggest a full privilege escalation exploit exists.Post-Exploitation Impact: Once the attacker achieves kernel-level code execution, they have full control over the system. They can disable security software, install persistent backdoors, exfiltrate sensitive data, or move laterally within the network. The high impact scores (C:H/I:H/A:H) reflect the severity of a complete system compromise.
Impact Assessment
The impact of CVE-2026-94403 is severe. A successful exploit allows a local attacker with low privileges to gain kernel-level code execution, effectively granting them SYSTEM privileges on the affected Windows host. This represents a complete compromise of the operating system's security boundaries. The CVSS score of 8.8 reflects the high confidentiality, integrity, and availability impacts, as well as the changed scope, which indicates that the vulnerability in the driver can affect the entire system.
Affected systems are those running ColorFul iGameCenter version 1.0.3.4 with the ene.sys driver loaded. This is likely limited to consumer-grade Windows desktops and laptops equipped with ColorFul iGame hardware, such as graphics cards and motherboards. The blast radius within an enterprise environment depends on how many endpoints have this software installed. While not typically a server-class application, iGameCenter may be present on developer workstations, gaming systems used for testing, or employee-owned devices that have been brought into the corporate network. In an enterprise context, a single compromised workstation can serve as a beachhead for lateral movement and further attacks. The fact that a public exploit exists and no patch is available elevates the risk significantly; attackers can easily adapt the exploit for their own campaigns.
Detection Guidance
Sigma Rule
title: Potential Exploitation Attempt of CVE-2026-94403 via ene.sys IOCTL
id: 8c9f2e1a-3b4d-4c5e-9f6a-7d8e9f0a1b2c
status: experimental
description: Detects suspicious IOCTL calls to the ene.sys driver that may indicate exploitation of CVE-2026-94403.
author: Threat Intelligence Team
date: 2026-01-15
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith: '\ene.sys'
condition: selection
falsepositives:
- Legitimate iGameCenter software interactions
level: high
tags:
- attack.privilege_escalation
- attack.t1068
- cve.2026-94403
YARA Rule
rule CVE_2026_94403_ENE_DRIVER
{
meta:
description = "Detects the vulnerable ene.sys driver version 1.0.3.4 associated with CVE-2026-94403"
author = "Threat Intelligence Team"
date = "2026-01-15"
reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-94403"
hash = "unknown"
strings:
$s1 = "ene.sys" ascii wide nocase
$s2 = "iGameCenter" ascii wide nocase
$s3 = "sub_140001AF0" ascii wide nocase
condition:
uint16(0) == 0x5A4D and
filesize < 2MB and
any of them
}
Suricata IDS Rule
alert local any any -> any any (msg:"Potential Local Exploitation Attempt of CVE-2026-94403 via ene.sys IOCTL"; flow:to_server; content:"|22 00 00 00|"; depth:4; classtype:attempted-admin; sid:10000001; rev:1;)
Note: This is a placeholder rule. Since the vulnerability is local (IOCTL), network detection is not applicable. The rule above is provided for completeness but should not be expected to fire on local IOCTL traffic. Detection should focus on endpoint logs.
Elastic Detection
process where process.name == "ene.sys" and process.args_count > 0
Note: This EQL query is a basic example. Kernel drivers do not typically generate process events with arguments. More effective detection would involve monitoring for suspicious IOCTL requests via Windows security auditing or Sysmon with driver load events.
Splunk SPL Query
index=main source="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventID=6
| search ImageLoaded="*\\ene.sys"
| table _time, ComputerName, ImageLoaded, Hashes
Note: This query detects the loading of the ene.sys driver, which is a prerequisite for exploitation. It does not detect the exploitation itself.
Wazuh OSSEC Rule
<group name="windows,cve-2026-94403,">
<rule id="100001" level="12">
<if_sid>60000</if_sid>
<field name="win.eventdata.imageLoaded">\\ene.sys</field>
<description>CVE-2026-94403: Vulnerable ColorFul ene.sys driver loaded - possible exploitation risk.</description>
<mitre>
<id>T1068</id>
</mitre>
</rule>
</group>
Mitigation & Patch Guidance
Patch confidence: 0/4 (UNPATCHED — no patch evidence from any tracked source).
Immediate Mitigations:
- Identify all systems with ColorFul iGameCenter installed. If the software is not essential for business operations, uninstall it and remove the
ene.sysdriver. - If the software is required, restrict local interactive logon privileges to trusted users only. This reduces the attack surface, as the attacker must already have local access and low privileges.
- Implement application whitelisting to prevent unauthorized executables from running, which could be used to deliver the exploit.
- Monitor for the presence of the
ene.sysdriver and for unusual IOCTL activity targeting it. Use the detection rules provided as a starting point, but be aware that endpoint detection and response (EDR) tools with kernel-level visibility are better suited for detecting this class of attack.
- Identify all systems with ColorFul iGameCenter installed. If the software is not essential for business operations, uninstall it and remove the
Patch/Upgrade Steps:
- No patch is currently available. The vendor, ColorFul, was contacted but did not respond. Monitor the vendor's official website and support channels for any future updates.
- In the absence of a vendor patch, consider removing the vulnerable driver manually from affected systems. This can be done by uninstalling iGameCenter and then verifying that
ene.sysis no longer present inC:\Windows\System32\drivers\. If the file remains, it may need to be deleted manually (after ensuring it is not in use) or via a driver removal tool.
Long-term Hardening:
- Enforce the principle of least privilege. Ensure that users operate with standard user accounts and not administrative privileges, as the vulnerability requires only low privileges to exploit.
- Enable Hypervisor-protected Code Integrity (HVCI) and Credential Guard on Windows 10/11 systems. These features can make kernel exploitation more difficult by preventing unauthorized code from running in kernel mode.
- Keep operating systems and third-party software up to date. While this specific driver is unpatched, other vulnerabilities may be addressed.
- Conduct regular audits of installed software and drivers, especially on systems that are not centrally managed. Remove unnecessary or outdated applications.
- For enterprise environments, consider blocking the installation of consumer-grade hardware utility software unless explicitly approved and managed.
References
- NVD Entry: https://nvd.nist.gov/vuln/detail/CVE-2026-94403
- CWE-822: Untrusted Pointer Dereference: https://cwe.mitre.org/data/definitions/822.html
- MITRE ATT&CK T1068: Exploitation for Privilege Escalation: https://attack.mitre.org/techniques/T1068/
- Vendor Website (ColorFul iGameCenter): https://www.colorful.cn/ (monitor for updates)
- Public Exploit (referenced by NVD, exact location not disclosed): The NVD description states "The exploit has been made available to the public and could be used for attacks." No specific URL is provided in the data.
What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.
💣 PoC CODE AVAILABLE
Exploit code for this CVE is tracked in our database.
Access poc_code via API Pro.