dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2026-26111

HIGH · 8.0 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 6.2.9200.25973 / 10.0.14393.8957 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
Integer overflow or wraparound in Windows Routing and Remote Access Service (RRAS) allows an authorized 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

Integer overflow or wraparound vulnerability in Windows Routing and Remote Access Service (RRAS) allows an authorized attacker to execute arbitrary code over a network by exploiting the memory handling flaw in the RRAS component.

MitigationApply Microsoft security patches for this vulnerability when available; 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 Server 2012Operating system
Affected:< 6.2.9200.25973= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8957
Windows Server 2019Operating system
Affected:< 10.0.17763.8511
Windows Server 2022Operating system
Affected:< 10.0.20348.4893
Windows Server 2025Operating system
Affected:< 10.0.26100.32522

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Windows Server version
    Run 'winver' from command prompt or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows Server build number
    Affected if The installed version falls below any of these thresholds: Server 2012 R2 < 6.2.9200.25973, Server 2016 < 10.0.14393.8957, Server 2019 < 10.0.17763.8511, Server 2022 < 10.0.20348.4893, Server 2025 < 10.0.26100.32522
  2. Verify RRAS service status
    Open Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell to check if the RemoteAccess service is installed
    Affected if The RemoteAccess service (RRAS) is present on the system
  3. Check if RRAS is running or enabled
    Run 'Get-Service RemoteAccess' and check the Status field, or check service startup type via 'sc query RemoteAccess'
    Affected if The RemoteAccess service is in a Running state or set to Automatic startup
  4. Confirm RRAS configuration
    Run 'netsh routing ip show status' or check Server Manager > Remote Access to see if routing or VPN features are actively configured
    Affected if RRAS is configured with active routing or remote access policies

The system is vulnerable if it runs an affected Windows Server version AND has RRAS installed, regardless of whether the service is currently running, as the vulnerable code is present in the component.

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 6.2.9200.25973 / 10.0.14393.8957 / 10.0.17763.8511 or later
Fixed in 6.2.9200.2597310.0.14393.895710.0.17763.8511
Interim mitigation

Apply Microsoft security patches for this vulnerability when available; if RRAS is not required, disable the service to reduce attack surface.

Recommended fix High confidence
  1. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2026-26111 to locate the applicable security update KB article
  2. Identify the correct KB article for your Windows Server version (2012 R2, 2016, 2019, 2022, or 2025)
  3. Download and install the security update from Microsoft Update Catalog or via Windows Update
  4. Restart the server after applying the update to ensure the RRAS component is fully updated
  5. Verify the installed version matches or exceeds the fixed version: Server 2012 R2: 6.2.9200.25973, Server 2016: 10.0.14393.8957, Server 2019: 10.0.17763.8511, Server 2022: 10.0.20348.4893, Server 2025: 10.0.26100.32522
Caveat Standard Windows security patch; apply during maintenance window as patches may require restart

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

Fix this in Windows Server 2012 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-2026-26111 — 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-2026-26111 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