CVE-2026-3609: XIGNCODE3 xhunter1.sys kernel driver contains a Privilege Escalation Vulnerability
Wellbia's XIGNCODE3 xhunter1.sys kernel driver, version 10.0.10011.16384 through 2023.12.7.78, privilege escalation vulnerability provides access to the IRP_MJ_WRITE command interface, which allows any user process to request a PROCESS_ALL_ACCESS.
Note: KVE 2023-5589 (https://krcert.or.kr) was initially issued for version 10.0.10011.16384, but the vulnerability was not fully remediated and remains in version 2023.12.7.78.
Security readout for executives and security teams
Plain-English summary
A vulnerable XIGNCODE3 Windows kernel driver lets code already running under a low-privileged account obtain excessive access to processes. This can help an attacker expand control after an initial compromise. It is a local privilege-escalation issue, not a directly remote attack, and the bundle reports no active exploitation.
Executive priority
Schedule targeted discovery and remediation promptly rather than treating this as an emergency remote vulnerability. Accelerate remediation where untrusted or low-privileged code may execute, because the flaw can amplify an existing foothold. Request vendor confirmation before declaring later versions safe.
Technical view
The xhunter1.sys driver exposes an IRP_MJ_WRITE interface through which any user process can request PROCESS_ALL_ACCESS. The stated affected range is 10.0.10011.16384 through 2023.12.7.78. CVSS 3.1 scores it 5.3 because exploitation is local, requires low privileges, needs no user interaction, and has limited confidentiality and integrity impact.
Likely exposure
Windows systems containing an affected xhunter1.sys version are potentially exposed. An attacker must already execute code locally with low privileges. Systems without this driver are not exposed to this CVE. The bundle does not identify affected applications, deployment prevalence, or confirmed-safe versions.
Exploitation context
The bundle does not report active exploitation, and KEV is false. Public researcher references are provided, but the supplied evidence does not establish weaponized exploitation or prevalence. The required local foothold makes this primarily a post-compromise escalation path.
Researcher notes
The CVE states that remediation for KVE 2023-5589 was incomplete and the flaw remained in 2023.12.7.78. However, the structured affected entry lists only 10.0.10011.16384, conflicting with the narrative range. The CWE mappings cover privilege assignment, authorization, and permissions. No vendor patch version is supplied.
Mitigation direction
Inventory endpoints for xhunter1.sys and record each installed driver version.
Seek current Wellbia guidance and apply only vendor-confirmed remediation.
Disable or remove the affected driver where operationally acceptable, after compatibility testing.
Restrict local account access on exposed systems until remediation is confirmed.
Validation and detection
Confirm xhunter1.sys presence and compare its version with the stated affected range.
Verify vendor-confirmed updates replace the vulnerable driver and persist after reboot.
Confirm unprivileged processes cannot obtain unrestricted handles through the driver interface.
Review endpoint telemetry for unexpected privileged process-handle access associated with xhunter1.sys.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-266: 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.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
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.