CVE-2026-29923
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe pstrip64.sys driver in EnTech Taiwan PowerStrip version 3.90.736 and below contains a privilege escalation vulnerability where a crafted IOCTL request allows unprivileged local users to map arbitrary physical memory into their address space and modify kernel structures, achieving SYSTEM-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if PowerStrip is installedLook for PowerStrip installation directory (typically C:\Program Files\PowerStrip or C:\Program Files (x86)\PowerStrip), check Add/Remove Programs in registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall), or look for pstrip64.sys driver file in System32\driversAffected if PowerStrip is found installed on the system
-
Determine PowerStrip versionOpen the installed PowerStrip directory and locate version information in the executable properties (right-click powerstrip.exe > Properties > Details), or check the driver file version property of pstrip64.sysAffected if Version is 3.90.736 or lower
-
Verify pstrip64.sys driver presenceCheck for pstrip64.sys in C:\Windows\System32\drivers\ directory. Right-click the file, go to Properties > Details to view file versionAffected if The pstrip64.sys driver file exists on the system
-
Check if driver is loadedOpen Command Prompt as Administrator and run 'sc query pstrip64' or check Device Manager for hidden/non-plug-and-play drivers. Also check 'driverquery /v' output for pstrip64Affected if The pstrip64 driver is currently loaded in memory
A user is affected if PowerStrip version 3.90.736 or below is installed with the pstrip64.sys driver present, regardless of whether the driver is currently loaded.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or uninstall PowerStrip if possible; if required, run the application with restricted privileges and consider implementing kernel patch protection or AppLocker policies to block untrusted driver loading.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29923 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-29923 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data