dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-47987

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.10240.21073 / 10.0.14393.8246 or later.
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
Heap-based buffer overflow in Windows Cred SSProvider Protocol 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 heap-based buffer overflow vulnerability exists in Windows Credential Security Support Provider (CredSSP) protocol. An authorized local attacker can exploit this by overflowing a heap buffer to execute arbitrary code with elevated privileges.

MitigationApply the relevant Windows security update addressing the CredSSP vulnerability; restrict local system access to authorized and trusted personnel only.

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.21073
Windows 10 1607Operating system
Affected:< 10.0.14393.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652

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. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify your Windows version and build number. Compare the build number to the affected version thresholds listed in the CVE (e.g., Windows 10 1809 requires build < 10.0.17763.7558)
    Affected if Your Windows build number is lower than the threshold for your specific Windows release (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  2. Verify CredSSP is enabled
    Open Services (services.msc) and locate 'Credential Security Support Provider' (CredSSP). Check if the service exists and its status. Alternatively, check registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CredSSP
    Affected if CredSSP service exists and is running (the vulnerability requires CredSSP to be present on the system)
  3. Check Remote Desktop configuration
    Run 'SystemPropertiesRemote' or check registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections to see if Remote Desktop is enabled
    Affected if Remote Desktop is enabled, as CredSSP is commonly used by RDP for credential delegation

You are affected if your Windows build is below the threshold for your version AND CredSSP is enabled on your system.

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.21073 / 10.0.14393.8246 / 10.0.17763.7558 or later
Fixed in 10.0.10240.2107310.0.14393.824610.0.17763.7558
Interim mitigation

Apply the relevant Windows security update addressing the CredSSP vulnerability; restrict local system access to authorized and trusted personnel only.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21073+ | Windows 10 1607: 10.0.14393.8246+ | Windows 10 1809: 10.0.17763.7558+ | Windows 10 21h2: 10.0.19044.6093+ | Windows 10 22h2: 10.0.19045.6093+ | Windows 11 22h2: 10.0.22621.5624+ | Windows 11 23h2: 10.0.22631.5624+ | Windows 11 24h2: 10.0.26100.4652+

  1. Identify your current Windows version and build number (winver command)
  2. Determine which affected version bracket your system falls into from the list: 1507, 1607, 1809, 21h2, 22h2, 11-22h2, 11-23h2, or 11-24h2
  3. Apply the corresponding Windows security update from Microsoft Update Catalog or Windows Update that includes the fix for CVE-2025-47987
  4. Restart the system to complete the update installation
  5. Verify the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update - minimal risk; ensure backups of critical data before applying updates

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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