dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-21323

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 10.0.10240.20890 / 10.0.14393.7699 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

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 Kernel Memory Information Disclosure 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
How this class of weakness works · CWE-532

Sensitive values — secrets, tokens, session identifiers, personal data — are written into log files, so anyone with access to the logs, which is often a broad group, obtains them. It turns a routine diagnostic into a credential leak. The fix is redacting sensitive data before it is logged and tightly restricting who can read the logs.

General guidance for the sensitive information in logs class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 10 1507Operating system
Affected:< 10.0.10240.20890
Windows 10 1607Operating system
Affected:< 10.0.14393.7699
Windows 10 1809Operating system
Affected:< 10.0.17763.6775
Windows 10 21h2Operating system
Affected:< 10.0.19044.5371
Windows 10 22h2Operating system
Affected:< 10.0.19045.5371
Windows 11 22h2Operating system
Affected:< 10.0.22621.4751
Windows 11 23h2Operating system
Affected:< 10.0.22631.4751
Windows 11 24h2Operating system
Affected:< 10.0.26100.2894

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
None
Availability
None

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

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.10240.20890 / 10.0.14393.7699 / 10.0.17763.6775 or later
Fixed in 10.0.10240.2089010.0.14393.769910.0.17763.6775
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Apply security update KB5055528 (or subsequent relevant security update for your specific Windows version)

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install all pending security updates, specifically the update for CVE-2025-21323
  3. Alternatively, download the specific security update from the Microsoft Update Catalog: https://catalog.update.microsoft.com/v7/site/Search.aspx?q=CVE-2025-21323
  4. Restart the system after installing the update
  5. Verify the update was installed by checking Windows Update history or running: Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 1

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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