Windows 11 version 22H2: Reliance on Untrusted Inputs in a Security Decision
CVE-2025-53717 is a high-severity reliance on untrusted inputs in a security decision vulnerability in Windows 11 version 22H2 from Microsoft, 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. The record lists version 10.0.22621.6060 as the first without the flaw, so updating Windows 11 version 22H2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.35% 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
- Update Windows 11 version 22H2 to 10.0.22621.6060 or a later version.
- Update Windows 11 version 22H3 to 10.0.22631.6060 or a later version.
- Update Windows 11 Version 23H2 to 10.0.22631.6060 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.6060 | 10.0.22621.6060 |
| Microsoft | Windows 11 version 22H3 | 10.0.22631.0 up to, but not including, 10.0.22631.6060 | 10.0.22631.6060 |
| Microsoft | Windows 11 Version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.6060 | 10.0.22631.6060 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.6899 | 10.0.26100.6899 |
| Microsoft | Windows 11 Version 25H2 | 10.0.26200.0 up to, but not including, 10.0.26200.6899 | 10.0.26200.6899 |
| Microsoft | Windows 11 22h2 | before 10.0.22621.6060 | 10.0.22621.6060 |
| Microsoft | Windows 11 23h2 | 10.0.22631.6060 and earlier | Not stated |
| Microsoft | Windows 11 24h2 | before 10.0.26100.6899 | 10.0.26100.6899 |
| Microsoft | Windows 11 25h2 | before 10.0.26200.6899 | 10.0.26200.6899 |
Version data comes from the organisation that assigned the CVE. 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 CNA (microsoft.com).
Official description
Reliance on untrusted inputs in a security decision in Windows Virtualization-Based Security (VBS) Enclave allows an authorized attacker to elevate privileges locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reliance on Untrusted Inputs in a Security Decision
The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. With a stateless protocol such as HTTP, use a framework that maintains the state for you. Examples include ASP.NET View State and the OWASP ESAPI Session Management feature. Be careful of language features that provide state support, since these might be provided as a convenience to the programmer and may not be considering security.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
More Reliance on Untrusted Inputs in a Security Decision vulnerabilities (CWE-807)
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 Windows 11 version 22H2
- 7.0 High severity
- 7.8 High severity
- 7.0 High severity
- 7.7 High severity
- 7.0 High severity
- 7.0 High severity
Recent Reliance on Untrusted Inputs in a Security Decision vulnerabilities
- 7.5 High severity
- 8.1 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.1 High severity
- 7.2 High severity
Spotted an error? Tell us.