dbcve.org
Windows 10Operating system · Microsoft

CVE-2022-24486

HIGH · 7.8 CVSS v3.1 Published 2022-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Kerberos Elevation of Privilege Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Windows Kerberos elevation of privilege vulnerability with CVSS 7.8. The vulnerability allows an authenticated attacker to elevate privileges via the Windows Kerberos implementation, likely through manipulation of Kerberos ticket handling or authentication flows.

MitigationApply the Microsoft security update for CVE-2022-24486 to affected Windows systems. Validate Kerberos authentication functionality post-patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10Operating system
Affected:all versions= 20h2= 21h1= 21h2= 1607= 1809= 1909
Windows 11Operating system
Affected:all versions
Windows Server 2016Operating system
Affected:all versions= 20h2
Windows Server 2019Operating system
Affected:all versions
Windows Server 2022Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build number
    Affected if The version matches any of the affected releases: Windows 10 (versions 1607, 1809, 1909, 20h2, 21h1, 21h2), Windows 11, Windows Server 2016, Windows Server 2019, or Windows Server 2022
  2. Verify Kerberos authentication is in use
    Check if the system is domain-joined by running 'echo %USERDOMAIN%' or 'systeminfo | findstr /C:"Domain"'. Active Directory domain membership enables Kerberos authentication by default
    Affected if The system is joined to an Active Directory domain, as Kerberos is the primary authentication protocol in AD environments
  3. Confirm the security update is installed
    Run 'Get-HotFix -Id KB5011567' or 'wmic qfe list | findstr "5011567"' to check if the CVE-2022-24486 patch is present
    Affected if The security update KB5011567 is NOT installed on the system
  4. Check alternative patch knowledge base
    Run 'Get-HotFix' or 'wmic qfe list' to enumerate all installed updates and look for March 2022 cumulative updates or later security patches
    Affected if No March 2022 or later cumulative security updates are installed, indicating the system is missing the vulnerability fix

A system is affected if it runs any affected Windows version, is domain-joined (using Kerberos), and lacks the KB5011567 or later security update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security update for CVE-2022-24486 to affected Windows systems. Validate Kerberos authentication functionality post-patch.

Fix this in Windows 10 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24486 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24486 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data