dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-49086

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.14393.7606 / 10.0.17763.6659 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 service that handles VPN connections and routing. An unauthenticated attacker could send specially crafted packets to a vulnerable RRAS server to execute arbitrary code with elevated privileges.

MitigationApply the Microsoft security update for CVE-2024-49086 from the November 2024 patch Tuesday release. If immediate patching is not possible, consider disabling RRAS if not required or restricting network access to RRAS servers.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7606
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022Operating system
Affected:< 10.0.20348.2966
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1308
Windows Server 2025Operating system
Affected:< 10.0.26100.2605

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. Confirm RRAS is installed
    Open Server Manager, go to Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell to check if the Routing role is installed
    Affected if RRAS is installed and the server version falls within the affected ranges below
  2. Check Windows Server version
    Run 'winver' from command prompt, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in command prompt, or use 'Get-ComputerInfo | select WindowsProductName, WindowsVersion' in PowerShell
    Affected if Version is Windows Server 2016 < 10.0.14393.7606, Server 2019 < 10.0.17763.6659, Server 2022 < 10.0.20348.2966, Server 2022 23h2 < 10.0.25398.1308, or Server 2025 < 10.0.26100.2605 (or unpatched Server 2008/2012)
  3. Verify RRAS service status
    Run 'Get-Service -Name RemoteAccess' in PowerShell or open Services.msc and check the RemoteAccess service status
    Affected if The RemoteAccess service (RRAS) is running
  4. Check for security update installation
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to list recent security updates, or check Windows Update history for November 2024 Security Updates
    Affected if No November 2024 security update for CVE-2024-49086 is installed

The server is affected if RRAS is installed and running on a vulnerable Windows Server version (2016/2019/2022/2022 23h2/2025 below the specified build numbers, or unpatched 2008/2012) AND the November 2024 security update has not been applied.

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.7606 / 10.0.17763.6659 / 10.0.20348.2966 or later
Fixed in 10.0.14393.760610.0.17763.665910.0.20348.2966
Interim mitigation

Apply the Microsoft security update for CVE-2024-49086 from the November 2024 patch Tuesday release. If immediate patching is not possible, consider disabling RRAS if not required or restricting network access to RRAS servers.

Recommended fix High confidence

Windows Server 2016: 10.0.14393.7606 | Windows Server 2019: 10.0.17763.6659 | Windows Server 2022: 10.0.20348.2966 | Windows Server 2022 23h2: 10.0.25398.1308 | Windows Server 2025: 10.0.26100.2605 (or later)

  1. Identify the affected Windows Server version by running 'winver' or checking System Properties
  2. Ensure you have backups and/or restore points before applying updates
  3. Apply the latest cumulative security update from Windows Update or your WSUS server that addresses CVE-2024-49086
  4. Alternatively, manually download and install the specific security update from the Microsoft Update Catalog for your Windows Server version
  5. Restart the server as required by the security update to complete the remediation
  6. Verify the update was installed successfully by checking the installed updates or running 'systeminfo | findstr KB'
  7. Confirm the RRAS service is running properly after restart
Caveat Standard Windows cumulative updateapply may require downtime; test in staging environment before production deployment

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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