# CVE-2026-6102: MSI Center NTIOLib_X64 Origin Validation Error Local Privilege Escalation Vulnerability

> Local attackers can escalate privileges to SYSTEM via insufficient origin validation in the MSI Center NTIOLib_X64 driver.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 29 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-9g9f-3pvm-h8r6

## What is CVE-2026-6102?

CVE-2026-6102 is a high-severity vulnerability in MSI Center, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MSI Center NTIOLib_X64 Origin Validation Error Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of MSI Center. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.

The specific flaw exists within the NTIOLib_X64.sys driver. The issue results from insufficient validation of the origin of commands. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-28935.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2026-6102 being exploited?

There is no known exploitation of CVE-2026-6102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6102 is a high-severity vulnerability in MSI Center, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6102 in the wild and no public exploit code.

Affected product: MSI Center. 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-6102/ (Markdown: https://insights.sbomify.com/CVE-2026-6102/index.md)
```

## Sources

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

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