# CVE-2026-15430: CVE-2026-15430

> A local unprivileged attacker can exploit improper access control in the XIGNCODE3 driver to escalate privileges to SYSTEM and extract credentials.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-gmfc-jwm3-239r

## What is CVE-2026-15430?

CVE-2026-15430 is a medium-severity vulnerability in Wellbia XIGNCODE3, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control in the IRP_MJ_WRITE command interface in
Wellbia XIGNCODE3 xhunter2.sys, version 2026.6.1.192, allows a local, unprivileged attacker to achieve local privilege escalation to
NT AUTHORITY\SYSTEM, extract credentials from PPL-protected
lsass.exe, and terminate PPL-protected security processes.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-284 (Improper Access Control), CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-15430 being exploited?

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

Public exploit code:

- PoCs for Wellbia XIGNCODE3 anti-cheat xhunter driver family - xhunter1.sys v2023.12.7.78 and xhunter2.sys v2026.6.1.192 (CVE-2026-15430, CVE-2026-3609). (github_poc): https://github.com/BlackSnufkin/AxHunter

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15430 is a medium-severity vulnerability in Wellbia XIGNCODE3, published on 3 Aug 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-15430 in the wild and no public exploit code.

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

## Sources

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

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