# CVE-2026-29923: Privilege escalation in n/a

> Local attackers can escalate privileges to SYSTEM by exploiting a crafted IOCTL request in the PowerStrip driver to map arbitrary physical memory.

- **Severity:** High 7.8 (`CVSS:3.1/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:** 9 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-g859-2xvj-jr82

## What is CVE-2026-29923?

CVE-2026-29923 is a high-severity vulnerability in n/a, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The pstrip64.sys driver in EnTech Taiwan PowerStrip <=3.90.736 allows local users to escalate privileges to SYSTEM via a crafted IOCTL request enabling unprivileged users to map arbitrary physical memory into their address space and modify critical kernel structures.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-29923 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29923 exists.

Public exploit code:

- A newly discovered vulnerable driver, pstrip64.sys (CVE-2026-29923) allows an unprivileged user to escalate privileges to SYSTEM via a crafted IOCTL request  (github_poc): https://github.com/athenasec16/CVE-2026-29923
- The pstrip64.sys kernel driver exposes an IOCTL that allows low-privileged users to map arbitrary ranges of physical memory into their own virtual address space. This primitive allows full read/write access to the system's physical RAM, enabling attackers to modify   critical kernel structures and escalate privileges to NT AUTHORITY\SYSTEM. (github_poc): https://github.com/Smarttfoxx/CVE-2026-29923
- https://github.com/mein-0/cve-2026-29923 (github_poc): https://github.com/mein-0/cve-2026-29923

## Fix prompt for AI coding agents

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

What it is: CVE-2026-29923 is a high-severity vulnerability in n/a, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-29923 exists.

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

## Sources

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

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