dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49668

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.14393.8246 / 10.0.17763.7558 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
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 affected service.

MitigationApply Microsoft security updates for RRAS when available; if RRAS is not required, disable the service; implement network-level filtering to restrict exposure to untrusted networks.

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.8246
Windows Server 2019Operating system
Affected:< 10.0.17763.7558
Windows Server 2022Operating system
Affected:< 10.0.20348.3932
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1732
Windows Server 2025Operating system
Affected:< 10.0.26100.4652

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) or run 'Get-Service RemoteAccess' in PowerShell. Check if the Remote Access service (RRAS) is installed and running.
    Affected if RRAS is installed and running - the vulnerability only affects systems with RRAS enabled
  2. Confirm Windows Server version
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion' in PowerShell. Note the exact build number (e.g., 10.0.14393.xxxx).
    Affected if Version cannot be determined or does not match the affected Windows Server products listed
  3. Compare against affected version ranges
    Execute 'systeminfo' or check the version from step 2. Compare your full build number (e.g., 10.0.14393.8246) against the affected ranges: Server 2016 < 10.0.14393.8246, Server 2019 < 10.0.17763.7558, Server 2022 < 10.0.20348.3932, Server 2022 23h2 < 10.0.25398.1732, Server 2025 < 10.0.26100.4652. Server 2008/2012 all versions are affected.
    Affected if Your Windows Server build number falls within an affected range or you are on Server 2008/2012 with RRAS enabled
  4. Assess network exposure
    Check if RRAS ports are exposed to untrusted networks. Review firewall rules for RRAS-related services (typically ports associated with Routing and Remote Access). Use 'netsh advfirewall firewall show rule name=all' or check VPN/RRAS firewall rules.
    Affected if RRAS is accessible from untrusted networks - this is required for remote exploitation

You are affected if RRAS is enabled AND your Windows Server version falls within the affected build ranges (or is Server 2008/2012) AND the service is network-accessible.

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.8246 / 10.0.17763.7558 / 10.0.20348.3932 or later
Fixed in 10.0.14393.824610.0.17763.755810.0.20348.3932
Interim mitigation

Apply Microsoft security updates for RRAS when available; if RRAS is not required, disable the service; implement network-level filtering to restrict exposure to untrusted networks.

Recommended fix High confidence

Windows Server 2016 to build 10.0.14393.8246 or later; 2019 to build 10.0.17763.7558 or later; 2022 to build 10.0.20348.3932 or later; 2022 23h2 to build 10.0.25398.1732 or later; 2025 to build 10.0.26100.4652 or later

  1. 1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine if your server version is affected by comparing the build number to the fixed versions: Windows Server 2016 (10.0.14393.8246), 2019 (10.0.17763.7558), 2022 (10.0.20348.3932), 2022 23h2 (10.0.25398.1732), 2025 (10.0.26100.4652)
  3. 3. For Windows Server 2008/2012 (all versions): These are end-of-life; migrate to a supported Windows Server version
  4. 4. For affected versions: Apply the appropriate Microsoft security update via Windows Update, WSUS, or download from Microsoft Update Catalog
  5. 5. Restart the server as required by the update
  6. 6. Verify the RRAS service is functioning correctly after the update
Caveat Windows Server 2008/2012 are end-of-life with no security updates - requires full migration to supported version; standard Windows update apply risks apply (test in staging first)

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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