dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-27492

HIGH · 7.0 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.20348.3453 / 10.0.22621.5189 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Secure Channel allows an authorized attacker to elevate privileges locally.

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

A race condition vulnerability exists in Windows Secure Channel (Schannel) where concurrent execution of code shares a resource without proper synchronization. An authorized attacker who already has local access can exploit this timing-sensitive vulnerability to elevate their privileges to a higher level, potentially gaining administrative or system-level access.

MitigationApply the Microsoft security update for CVE-2025-27492 through standard Windows Update or enterprise patch management systems. Prioritize patching for systems where untrusted users have local access.

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 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775
Windows Server 2022Operating system
Affected:< 10.0.20348.3453
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1551
Windows Server 2025Operating system
Affected:< 10.0.26100.3775

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Check Windows build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed build number
    Affected if Build number is lower than the fixed version for your Windows edition
  2. Identify exact Windows edition and version
    Note whether the system is Windows 11 (22h2, 23h2, or 24h2) or Windows Server (2022, 2022 23h2, or 2025) from System Properties or 'systeminfo' output
    Affected if Running any of the affected editions listed in the CVE
  3. For Windows 11 22h2: vulnerable if < 10.0.22621.5189; 23h2: vulnerable if < 10.0.22631.5189; 24h2: vulnerable if < 10.0.26100.3775; Server 2022: vulnerable if < 10.0.20348.3453; Server 2022 23h2: vulnerable if < 10.0.25398.1551; Server 2025: vulnerable if < 10.0.26100.3775
    Affected if Your exact build number falls below the threshold for your specific Windows edition

System is affected if running any Windows 11 or Windows Server version with a build number lower than the fixed version for that specific edition, as Schannel is a built-in component and the vulnerability applies to all such installations within the version ranges.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.20348.3453 / 10.0.22621.5189 / 10.0.22631.5189 or later
Fixed in 10.0.20348.345310.0.22621.518910.0.22631.5189
Interim mitigation

Apply the Microsoft security update for CVE-2025-27492 through standard Windows Update or enterprise patch management systems. Prioritize patching for systems where untrusted users have local access.

Recommended fix High confidence

Windows 11 22h2 build 10.0.22621.5189 or later | Windows 11 23h2 build 10.0.22631.5189 or later | Windows 11 24h2 build 10.0.26100.3775 or later | Windows Server 2022 build 10.0.20348.3453 or later | Windows Server 2022 23h2 build 10.0.25398.1551 or later | Windows Server 2025 build 10.0.26100.3775

  1. Verify current Windows build version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Windows Update and check for updates
  3. Alternatively, manually check for the specificKB that addresses CVE-2025-27492 on the Microsoft Update Catalog (catalog.update.microsoft.com)
  4. Install all available cumulative updates for your Windows version
  5. Reboot the system when prompted
  6. Confirm the installed build meets or exceeds the minimum fixed version for your product (e.g., 10.0.22621.5189 for Win11 22h2, 10.0.22631.5189 for Win11 23h2, 10.0.26100.3775 for Win11 24h2/Server 2025, 10.0.20348.3453 for Server 2022, 10.0.25398.1551 for Server 2022 23h2)
Caveat Standard Windows update risks - ensure backups and compatibility testing for business-critical applications before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27492 — 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-2025-27492 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