dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-55699

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
57/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
Exposure of sensitive information to an unauthorized actor in Windows Kernel allows an authorized attacker to disclose information 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

This is a Windows Kernel vulnerability that allows a local, authorized attacker to disclose sensitive information. The CVSS 5.5 indicates a local attack vector with low complexity, requiring low privileges. This represents an information disclosure flaw in the Windows kernel that could expose sensitive data to an attacker with local system access.

MitigationApply the Microsoft security update for CVE-2025-55699 through Windows Update or the relevant monthly security patch rollup. Verify the patch is deployed across affected Windows systems.

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 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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

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. Retrieve the installed Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' to display the OS version and build, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get detailed version information
    Affected if The displayed build number falls below the threshold for your specific Windows release (see version-specific thresholds below)
  2. Identify the Windows release version
    From the winver output, note the release name (such as 'Version 1507', 'Version 1607', 'Version 1809', 'Version 21H2', 'Version 22H2', 'Version 23H2', or 'Version 24H2')
    Affected if You are running any of these releases and the build number is below the corresponding threshold
  3. Compare build number against affected thresholds
    Match your build number to these thresholds: Windows 10 1507 requires < 10.0.10240.21161; Windows 10 1607 requires < 10.0.14393.8519; Windows 10 1809 requires < 10.0.17763.7919; Windows 10 21h2 requires < 10.0.19044.6456; Windows 10 22h2 requires < 10.0.19045.6456; Windows 11 22h2 requires < 10.0.22621.6060; Windows 11 23h2 requires <= 10.0.22631.6060; Windows 11 24h2 requires < 10.0.26100.6899
    Affected if Your installed build number is lower than the threshold for your specific Windows release

The system is affected if it runs any of the listed Windows versions and its build number is below the corresponding threshold, meaning it has not received the security update for CVE-2025-55699.

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.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the Microsoft security update for CVE-2025-55699 through Windows Update or the relevant monthly security patch rollup. Verify the patch is deployed across affected Windows systems.

Recommended fix Moderate confidence

Install the latest Windows Security Update containing the fix for CVE-2025-55699 (refer to Microsoft Security Response Center for the specific KB article for your Windows version)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates from Microsoft Update
  3. Alternatively, manually download the security update from the Microsoft Update Catalog (search for the relevant KB article for your Windows version)
  4. Restart the system after the update is installed to ensure the kernel patch is fully applied
  5. Verify the installed update by checking Windows Update history to confirm the security patch is present
Caveat Standard Windows security updates typically have minimal breaking changes; verify compatibility with critical line-of-business applications before deployment in production environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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