dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26205

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

CVE-2024-26205 is a remote code execution vulnerability in Windows Routing and Remote Access Service (RRAS). An attacker could exploit this to execute arbitrary code on affected Windows systems where RRAS is enabled, potentially gaining full control of the server.

MitigationApply the Microsoft security update for CVE-2024-26205 to all affected Windows servers. If RRAS is not required, disable or remove the feature to reduce the 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. Verify RRAS service status
    Open Services console (services.msc) and locate 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell. Check if the service is in a Running or Started state.
    Affected if RRAS service is enabled and running - only then is the system potentially vulnerable
  2. Confirm Windows build version
    Run 'winver' from Run dialog, or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell.
    Affected if Windows build number falls below the following thresholds: 10240.20596 (1507), 14393.6897 (1607), 17763.5696 (1809), 19044.4291 (21h2/22h2), 22000.2899 (Win11 21h2), 22621.3447 (Win11 22h2), 22631.3447 (Win11 23h2)
  3. Check RRAS server role configuration
    Open Server Manager on Windows Server, navigate to Tools > Routing and Remote Access, or run 'netsh routing ip show config' to view RRAS configuration status.
    Affected if RRAS server role is installed and configured - the vulnerability requires RRAS to be actively configured as a router or VPN server

System is affected only if RRAS is enabled AND the Windows build version is lower than the fixed build numbers for the respective Windows version.

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 Microsoft security update for CVE-2024-26205 to all affected Windows servers. If RRAS is not required, disable or remove the feature to reduce the attack surface.

Recommended fix High confidence

Upgrade to the specified build number or later for your Windows version (e.g., Windows 10 22h2 to 10.0.19045.4291 or later, Windows 11 23h2 to 10.0.22631.3447 or later)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Confirm the exact build number against the affected versions listed for CVE-2024-26205
  3. If running an affected version, apply the latest Windows Security Update via Windows Update (Settings > Update & Security > Windows Update)
  4. Alternatively, download and install the specific monthly security update from Microsoft Update Catalog that corresponds to your Windows version and includes the fix for CVE-2024-26205
  5. After installation, verify the build number matches or exceeds: 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 | Windows 11 22h2: 10.0.22621.3447 | Windows 11 23h2: 10.0.22631.3447
  6. If RRAS (Routing and Remote Access Service) is not required, consider disabling it via Server Manager (for Server) or Services.msc (for client) to reduce attack surface
Caveat Standard Windows update risks apply - test critical applications before deploying to production; ensure backups exist

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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