Local privilege escalation via undisclosed firmware access control
Published Aug 11, 2026 · Updated Aug 11, 2026
Improper access control in Intel Alias Checking Trusted Module firmware allows local users to escalate privileges on affected Xeon systems. Intel has not disclosed the firmware routine, missing authorization check, or constrained operation that causes the flaw. Exploitation requires a privileged user operating through startup code or SMM, has high complexity, and compromises confidentiality and integrity without interrupting availability.
Summary
What happened
Improper access control in Intel Alias Checking Trusted Module firmware allows local users to escalate privileges on affected Xeon systems. Intel has not disclosed the firmware routine, missing authorization check, or constrained operation that causes the flaw. Exploitation requires a privileged user operating through startup code or SMM, has high complexity, and compromises confidentiality and integrity without interrupting availability.
The record
- CVE
- CVE-2026-20898
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Alias Checking Trusted Module
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- admin
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