CVE-2026-69822: Windows Kerberos Elevation of Privilege Vulnerability
Numeric truncation error in Windows Kerberos allows an authorized attacker to elevate privileges locally.
Other sources
Windows Kerberos Elevation of Privilege Vulnerability
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.28000.2954Patch KB5124012 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.19045.7725Patch KB5122878 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26200.9445Patch KB5124008 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22631.7582Patch KB5122880 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.9445Patch KB5124008 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.19044.7725Patch KB5122878 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.33438Patch KB5122871 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.20348.5622Patch KB5122882 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.17763.9245Patch KB5122876
Event History
Frequently Asked Questions
Who can exploit this vulnerability?
An attacker must already be authorized on the affected system and have local access. The provided information does not indicate that unauthenticated or remote exploitation is possible.
What is the potential impact of successful exploitation?
Successful exploitation can allow local elevation of privilege. The supplied severity vector indicates high impacts to confidentiality, integrity, and availability.
Which systems should be assessed?
Assess deployments of Microsoft Windows 10, Windows 11, Windows Server 2019, Windows Server 2022, and Windows Server 2025. The provided data does not identify affected builds, editions, or configuration-specific exposure.