dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-64678

HIGH · 8.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Routing and Remote Access Service (RRAS) 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 heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows remote, unauthenticated attackers to execute arbitrary code by sending specially crafted network packets to the RRAS service. The vulnerability results from insufficient bounds checking when processing incoming network requests.

MitigationApply Microsoft security updates for this vulnerability immediately. Until patches are deployed, restrict network access to RRAS services via firewalls or network segmentation and monitor for indicators of compromise.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating system
Affected:all versions= r2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 if RRAS feature is installed
    Run PowerShell command: Get-WindowsOptionalFeature -Online -FeatureName RoutingAndRemoteAccess | Select-Object -Property State
    Affected if The State value is 'Enabled', indicating RRAS is installed and could be vulnerable
  2. Verify Windows version and build number
    Run winver or execute: [System.Environment]::OSVersion.Version.ToString() and [System.Environment]::OSVersion.Build.ToString()
    Affected if The version matches any of the affected Windows 10 or 11 releases listed in the CVE, and the build number is below the fixed thresholds (14393.8594, 17763.8027, 19044.6575, 19045.6575, 22631.6199, 26100.7092, or 26200.7092 depending on release)
  3. Confirm RRAS service status
    Open Services console (services.msc) or run: Get-Service RemoteAccess | Select-Object Status, StartType
    Affected if The RemoteAccess service is running (Status equals 'Running'), making the vulnerable code active
  4. Check network exposure of RRAS
    Run: netsh routing ip show interface or review firewall rules for RRAS-related ports (default ports 1723 for PPTP, 47 for GRE)
    Affected if RRAS is exposed to untrusted network interfaces, allowing remote attackers to send malicious packets

A system is affected if it runs a vulnerable Windows version with RRAS enabled and the service is accessible over the network.

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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply Microsoft security updates for this vulnerability immediately. Until patches are deployed, restrict network access to RRAS services via firewalls or network segmentation and monitor for indicators of compromise.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8594 | Windows 10 1809: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092

  1. Identify the current Windows version by running 'winver' or 'systeminfo'
  2. Open Windows Update (Settings > Update & Security > Windows Update)
  3. Check for and install the latest security updates from Microsoft
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog (catalog.update.microsoft.com) by searching for the CVE ID or KB number associated with this vulnerability
  5. After installation, restart the affected system to apply the patches
  6. Verify the installed version matches or exceeds the fixed version for your Windows edition

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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