Skip to main content

N A CVE-2026-29923

| EUVDEUVD-2026-21014 HIGH
Improper Privilege Management (CWE-269)
2026-04-09 mitre GHSA-g859-2xvj-jr82
7.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Gain standard user access
  2. Delivery
    Identify PowerStrip driver loaded
  3. Exploit
    Craft IOCTL payload for memory mapping
  4. Install
    Send request to pstrip64.sys device
  5. C2
    Map kernel memory to user space
  6. Execute
    Locate and modify process token
  7. Impact
    Escalate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Local user with standard privileges on Windows system running EnTech Taiwan PowerStrip version 3.90.736 or earlier with pstrip64.sys driver installed. No user interaction required. Attacker sends crafted IOCTL request to driver to map arbitrary physical memory and escalate to SYSTEM privileges.

Impact

Real-world risk is moderate and highly context-dependent. The CVSS base score of 7.8 reflects high impact (complete system compromise) but requires authenticated local access (PR:L), limiting attack surface to scenarios where an attacker already has a foothold. EPSS probability of 0.02% (5th percentile) suggests minimal automated exploitation activity, though the PacketStorm Security reference indicates documented exploit methodology exists. SSVC decision factors: exploitation status is POC-available (not active/widespread), technical impact is total system compromise, automatable exploitation is unlikely (requires local interactive session). Key risk multipliers: PowerStrip is discontinued/unsupported software (last update pre-2010), meaning no vendor patches will be released; organizations still running this for legacy display management have no remediation path except removal. In enterprise environments with application whitelisting and least-privilege enforcement, exploitation difficulty increases significantly. However, in gaming/enthusiast systems or poorly managed workstations where PowerStrip persists, the local privilege escalation becomes a viable post-exploitation pivot for ransomware operators or APT actors already inside the perimeter.

Exploit ScenarioDerived

An attacker who has already compromised a standard user account on a Windows workstation (via phishing, credential theft, or application vulnerability) discovers PowerStrip installed. Using the publicly documented exploit methodology from PacketStorm Security, they compile a weaponized program that sends specially crafted IOCTL requests to \Device\pstrip64. The driver processes the malicious request without privilege checks, allowing the attacker's user-mode process to map physical memory pages containing kernel structures. The attacker locates their own process token in kernel memory and modifies privilege bits to grant SeDebugPrivilege and SYSTEM-level access, then spawns a command shell running as NT AUTHORITY\SYSTEM with full administrative control over the machine.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 14, 2026

PowerStrip driver (pstrip64.sys) through version 3.90.736 enables authenticated local users to escalate privileges to SYSTEM by sending malicious IOCTL requests that map arbitrary physical memory into user-mode address space, allowing modification of kernel structures. EPSS score of 0.02% (5th percentile) indicates low automated exploitation likelihood, though publicly available exploit code exists (PacketStorm Security reference), making this a realistic threat in environments where PowerStrip is deployed and local access is possible. No CISA KEV listing indicates no confirmed widespread exploitation at time of analysis.

RemediationAI

No vendor-released patch exists or will be developed, as PowerStrip is discontinued and unmaintained since approximately 2009-2010. Primary remediation is complete removal of PowerStrip software from all systems, including uninstalling the application via Control Panel and verifying deletion of pstrip64.sys from the Windows drivers directory (typically C:\Windows\System32\drivers). Organizations requiring legacy display management should migrate to actively supported alternatives such as manufacturer-provided GPU utilities (NVIDIA Control Panel, AMD Radeon Software) or modern open-source tools. For air-gapped/isolated systems where removal is operationally complex, implement compensating controls: enforce least-privilege user accounts (no local admin rights), enable Windows Defender Application Control or AppLocker to block unauthorized driver loading, and deploy endpoint detection and response (EDR) tools with behavioral monitoring for IOCTL-based kernel exploitation attempts. Regularly audit installed drivers using Microsoft Vulnerable Driver Blocklist and apply latest Windows security updates to harden kernel attack surface.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

PowerStrip is a legacy display utility from EnTech Taiwan that includes a kernel-mode driver (pstrip64.sys) for low-level hardware interaction. The vulnerability stems from CWE-269 (Improper Privilege Management), where the driver exposes IOCTL handlers that fail to validate caller privileges or sanitize inputs controlling memory mapping operations. Windows IOCTL (Input/Output Control) interfaces allow user-mode applications to send commands to kernel drivers. When improperly secured, attackers can craft IOCTL requests to invoke privileged operations like mapping physical memory-bypassing CPU memory protection and enabling direct manipulation of kernel data structures such as process tokens, access control lists, or driver dispatch tables. This pattern is common in aging hardware utility drivers that predate modern Windows security models like HVCI and driver isolation.

Know when N A gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
CVSS changed
Apr 14, 2026 - 17:22 NVD
7.8 (HIGH)
CVE Published
Apr 09, 2026 - 00:00 nvd
N/A

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

PowerStrip driver versions through 3.90.736 contain a privilege escalation vulnerability that allows authenticated local users to gain SYSTEM-level access by exploiting kernel memory mapping via malicious IOCTL requests. Organizations running PowerStrip should immediately assess deployment scope, as publicly available exploit code reduces the barrier to attack for any user with local system access, potentially compromising sensitive data and system integrity.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict local system access through privileged access management (PAM) and principle of least privilege; (2) Implement kernel-mode driver signing enforcement and disable unsigned driver loading; (3) Monitor and alert on IOCTL requests to pstrip64.sys via EDR/HIPS solutions; (4) Apply OS-level privilege escalation detection rules; (5) Consider disabling PowerStrip entirely if alternative graphics drivers are available.

Threat Intelligence Overview

EPSS Score
0.0%
Top 95% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

59
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

More in N A

View all
CVE-2024-51092 CRITICAL POC
9.1 May 08

LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr

CVE-2025-15684 MEDIUM POC
5.5 Aug 12

Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han

CVE-2024-45257 HIGH POC
7.3 May 08

A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi

CVE-2025-15687 LOW POC
2.1 Aug 12

Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc

CVE-2025-15686 LOW POC
2.1 Aug 12

Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula

CVE-2025-67888 HIGH POC
7.3 May 08

Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root

CVE-2024-53326 HIGH POC
7.3 May 08

LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(

CVE-2026-38360 CRITICAL POC
9.8 May 08

Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti

CVE-2026-30623 CRITICAL POC
9.8 Jul 15

Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr

CVE-2026-67917 CRITICAL POC
9.8 Aug 17

SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg

CVE-2026-75337 CRITICAL POC
9.8 Aug 27

Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ

CVE-2026-31072 CRITICAL POC
9.8 May 19

Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy