Local code execution via improper driver authentication
Published Aug 11, 2026 · Updated Aug 11, 2026
Improper authentication in Intel PROSet/Wireless WiFi Software for Windows allows local users to execute code through a device driver. The flaw is within the Ring 2 device-driver layer, but Intel has not disclosed the affected routine, authentication decision, or rejected input. Local access by unprivileged software is sufficient without user interaction; exploitation exposes limited local data and produces high subsequent confidentiality impact.
Summary
What happened
Improper authentication in Intel PROSet/Wireless WiFi Software for Windows allows local users to execute code through a device driver. The flaw is within the Ring 2 device-driver layer, but Intel has not disclosed the affected routine, authentication decision, or rejected input. Local access by unprivileged software is sufficient without user interaction; exploitation exposes limited local data and produces high subsequent confidentiality impact.
The record
- CVE
- CVE-2026-20891
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel PROSet/Wireless WiFi Software
- Classifications
- CWE-287, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo