dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-26668

HIGH · 7.5 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 10.0.10240.20978 / 10.0.14393.7969 or later.
See remediation →
82/100
Remediation priority · High
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

Heap-based buffer overflow in Windows Routing and Remote Access Service (RRAS) allows an unauthenticated remote attacker to execute arbitrary code by sending specially crafted network packets to the RRAS service.

MitigationApply Microsoft security updates for CVE-2025-26668 when available, and restrict network exposure of systems running RRAS by using firewalls, network segmentation, or disabling RRAS if not required.

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.20978
Windows 10 1607Operating system
Affected:< 10.0.14393.7969
Windows 10 1809Operating system
Affected:< 10.0.17763.7136
Windows 10 21h2Operating system
Affected:< 10.0.19044.5737
Windows 10 22h2Operating system
Affected:< 10.0.19045.5737
Windows 11 22h2Operating system
Affected:< 10.0.22621.5189
Windows 11 23h2Operating system
Affected:< 10.0.22631.5189
Windows 11 24h2Operating system
Affected:< 10.0.26100.3775

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Verify if RRAS is installed and running
    Open Services (services.msc) and look for 'Routing and Remote Access' (RRAS) service, or run 'Get-Service RemoteAccess' in PowerShell. Also check 'Add Roles and Features' > 'Remote Access' role.
    Affected if RRAS service is installed and enabled - the vulnerability only affects systems with RRAS running
  2. Check Windows build version
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber' in PowerShell to obtain the exact build number (e.g., 19045.5737 for Windows 10 22h2).
    Affected if Build number is lower than the threshold for your Windows version: 10.0.10240.20978 (1507), 10.0.14393.7969 (1607), 10.0.17763.7136 (1809), 10.0.19044.5737 (21h2), 10.0.19045.5737 (22h2), 10.0.22621.5189 (11 22h2), 10.0.22631.5189 (11 23h2), or 10.0.26100.3775 (11 24h2)
  3. Confirm installed security update
    Run 'Get-HotFix | Where-Object {$_.Description -match "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recent security patches, or check Windows Update history for the specific KB addressing CVE-2025-26668.
    Affected if No security update for CVE-2025-26668 is installed and your version falls within the affected range

You are affected if RRAS is enabled and your Windows build version is below the threshold for your specific Windows release, or if the CVE-2025-26668 security update is not installed.

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.20978 / 10.0.14393.7969 / 10.0.17763.7136 or later
Fixed in 10.0.10240.2097810.0.14393.796910.0.17763.7136
Interim mitigation

Apply Microsoft security updates for CVE-2025-26668 when available, and restrict network exposure of systems running RRAS by using firewalls, network segmentation, or disabling RRAS if not required.

Recommended fix High confidence

Upgrade to the latest Cumulative Update for your Windows version; specific fixed builds are: Windows 10 1507 -> 10.0.10240.20978, Windows 10 1607 -> 10.0.14393.7969, Windows 10 1809 -> 10.0.17763.7136, Windows 10 21h2 -> 10.0.19044.5737, Windows 10 22h2 -> 10.0.19045.5737, Windows 11 22h2 -> 10.0.22

  1. 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. 2. Determine which version band your system falls into (Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2)
  3. 3. Apply the latest Microsoft security updates for your Windows version via Windows Update, or manually download and install the appropriate Cumulative Update from the Microsoft Update Catalog
  4. 4. Verify the installation was successful by checking that the build number matches or exceeds the fixed version for your release channel
  5. 5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update risks apply (update compatibility issues are rare but test in critical environments)

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-26668 — 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-26668 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