dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-29828

HIGH · 8.1 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.20348.3745 / 10.0.22621.5472 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Missing release of memory after effective lifetime in Windows Cryptographic Services allows an unauthorized attacker to execute code over a network.

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 memory leak vulnerability exists in Windows Cryptographic Services where memory is not properly released after its effective lifetime. This memory corruption can be exploited by an unauthorized remote attacker to execute arbitrary code over a network, potentially leading to complete system compromise.

MitigationApply the relevant Microsoft security patches for Windows Cryptographic Services once released. Prioritize patching systems exposed to network attack vectors given the remote code execution capability.

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.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270
Windows Server 2022Operating system
Affected:< 10.0.20348.3745
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1665
Windows Server 2025Operating system
Affected:< 10.0.26100.4270

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

CVSS:3.1/AV:N/AC:H/PR:N/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 version
    Run 'winver' from command prompt or 'systeminfo' and look at the OS Build number field, or run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion | Select-Object CurrentBuild,DisplayVersion,UBR' in PowerShell
    Affected if The build number is lower than the fixed version for your Windows edition (22h2: <22621.5472, 23h2: <22631.5472, 24h2: <26100.4270, Server 2022: <20348.3745, Server 2022 23h2: <25398.1665, Server 2025: <26100.4270)
  2. Identify exact Windows edition and version
    Run 'winver' or check System Properties to confirm whether you are on Windows 11 22h2, 23h2, 24h2, Windows Server 2022, Server 2022 23h2, or Server 2025
    Affected if The detected edition matches one of the affected products but the build version is below the corresponding fixed version
  3. Verify Cryptographic Services status
    Open Services console (services.msc) and check if 'Cryptographic Services' service is running, or run 'Get-Service CryptSvc' in PowerShell
    Affected if The service is running and the build version is below the fixed threshold - the vulnerability exists in this component

You are affected if your Windows build number is below the fixed version for your specific Windows edition and the Cryptographic Services service is enabled.

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.3745 / 10.0.22621.5472 / 10.0.22631.5472 or later
Fixed in 10.0.20348.374510.0.22621.547210.0.22631.5472
Interim mitigation

Apply the relevant Microsoft security patches for Windows Cryptographic Services once released. Prioritize patching systems exposed to network attack vectors given the remote code execution capability.

Recommended fix High confidence

Windows 11 22h2: build 10.0.22621.5472 or later | Windows 11 23h2: build 10.0.22631.5472 or later | Windows 11 24h2: build 10.0.26100.4270 or later | Windows Server 2022: build 10.0.20348.3745 or later | Windows Server 2022 23h2: build 10.0.25398.1665 or later | Windows Server 2025: build 10.0.26100

  1. Check current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Settings > Windows Update > Check for updates, or manually download the security update from the Microsoft Update Catalog (search for CVE-2025-29828)
  3. Install the cumulative security update for your Windows version
  4. Restart the system when prompted
  5. Verify the installation by checking the Windows version matches or exceeds: Windows 11 22h2: 10.0.22621.5472, Windows 11 23h2: 10.0.22631.5472, Windows 11 24h2: 10.0.26100.4270, Windows Server 2022: 10.0.20348.3745, Windows Server 2022 23h2: 10.0.25398.1665, Windows Server 2025: 10.0.26100.4270
Caveat Standard Windows cumulative update; no expected breaking changes for this security patch

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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