dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26200

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 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
Windows Routing and Remote Access Service (RRAS) Remote Code Execution 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 · moderate confidence

This is a remote code execution vulnerability in Windows Routing and Remote Access Service (RRAS), a Windows server role that handles routing and VPN capabilities. The vulnerability allows an attacker to execute arbitrary code on affected Windows servers where RRAS is enabled, likely through malformed network requests to the RRAS service.

MitigationApply the relevant Microsoft security updates for CVE-2024-26200 to all affected Windows servers. If RRAS is not required, disable the service to reduce attack surface.

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.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

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. Determine if RRAS is enabled
    Open Services (services.msc) and locate 'Routing and Remote Access (RRAS)' service, or run 'Get-Service RemoteAccess' in PowerShell. Check if the service status is Running or if it's set to start automatically.
    Affected if RRAS service is installed and enabled (Running or set to Automatic start)
  2. Identify Windows build version
    Run 'winver' from the Run dialog, or run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell, or run 'systeminfo' in Command Prompt and look for the 'OS Version' line.
    Affected if The build number is below the fixed version for your Windows release
  3. Compare against affected version ranges
    Match your Windows release (1507, 1607, 1809, 21h2, 22h2 for Windows 10; 21h2, 22h2, 23h2 for Windows 11) and build number to the affected ranges: Windows 10 1507 < 10.0.10240.20596, 1607 < 10.0.14393.6897, 1809 < 10.0.17763.5696, 21h2 < 10.0.19044.4291, 22h2 < 10.0.19045.4291. Windows 11 21h2 < 10.0.22000.2899, 22h2 < 10.0.22621.3447, 23h2 < 10.0.22631.3447.
    Affected if Your Windows build version falls below the fixed build for your specific Windows release

Your environment is affected if RRAS is enabled and your Windows build version is lower than the fixed build for your Windows release.

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.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply the relevant Microsoft security updates for CVE-2024-26200 to all affected Windows servers. If RRAS is not required, disable the service to reduce attack surface.

Recommended fix High confidence

Apply the Microsoft security update that addresses CVE-2024-26200 (minimum fixed versions: Windows 10 1507: 10.0.10240.20596 | Windows 10 1607: 10.0.14393.6897 | Windows 10 1809: 10.0.17763.5696 | Windows 10 21h2: 10.0.19044.4291 | Windows 10 22h2: 10.0.19045.4291 | Windows 11 21h2: 10.0.22000.2899

  1. Obtain the Microsoft security update for CVE-2024-26200 from the Microsoft Security Response Center (msrc.microsoft.com) or Windows Update
  2. Apply the security update to the affected Windows system
  3. Restart the system if prompted to complete the installation
  4. Verify the update was installed successfully by checking the installed updates or system version
Caveat Standard Windows security update risks - test in staging environment before production deployment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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