Intel(R) Processors: Improper Access Control
CVE-2026-20716 is a high-severity improper access control vulnerability in Intel(R) Processors, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Intel(R) Processors versions: See references. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.09% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Intel(R) Processors you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on intel.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Intel(R) Processors | Intel(R) Processors | See references | Not stated |
| Intel | Xeon 634 Firmware | Not specified in the record | Not stated |
| Intel | Xeon 636 Firmware | Not specified in the record | Not stated |
| Intel | Xeon 638 Firmware | Not specified in the record | Not stated |
| Intel | Xeon 654 Firmware | Not specified in the record | Not stated |
| Intel | Xeon 656 Firmware | Not specified in the record | Not stated |
| Intel | Xeon 658x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 674x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 676x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 678x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 696x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 698x Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6315p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6325p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6333p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6337p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6349p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6353p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6357p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6369p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6377p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6503p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6503p-b Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6505p Firmware | Not specified in the record | Not stated |
| Intel | Xeon 6507p Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.2 | High | CNA (intel.com) |
| CVSS 3.1 | 7.0 | High | NVD |
Official description
Improper access control for some Intel(R) Processors within Ring 3: User Applications may allow an escalation of privilege. Simple hardware adversary with an authenticated user combined with a high complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present with special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Intel(R) Processors
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.2 High severity
Recent Improper Access Control vulnerabilities
- 7.2 High severity
- 7.8 High severity
- 7.4 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.