dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49657

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

A heap-based buffer overflow vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthorized remote attacker to execute arbitrary code. This is a memory corruption vulnerability in a core Windows networking service that handles VPN and routing functionality.

MitigationApply the relevant Windows security update when available. If RRAS is not required, disable the service. Implement network segmentation to limit exposure and monitor for indicators of compromise.

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 if RRAS is installed
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or run: Get-Service -Name 'RemoteAccess' in PowerShell
    Affected if RRAS service exists on the system - if present and running, the system could be vulnerable if version is affected
  2. Identify Windows Server version
    Run 'winver' in command prompt, or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in cmd, or query registry: reg query 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion'
    Affected if Version information will determine if it falls within affected product range (2008, 2012, 2016, 2019, 2022, 2022 23h2, 2025)
  3. Check build number
    Run 'systeminfo' and look at 'OS Version' field, or use PowerShell: [System.Environment]::OSVersion.Version.Build
    Affected if Compare build number against affected thresholds: Server 2016 < 14393, Server 2019 < 17763, Server 2022 < 20348, Server 2022 23h2 < 25398, Server 2025 < 26100 - any build below these thresholds indicates potential vulnerability if RRAS is enabled
  4. Confirm RRAS service status
    In Services console, check if 'Routing and Remote Access' service is running, or run: Get-Service -Name 'RemoteAccess' | Select-Object Status
    Affected if If service is started or set to automatic, the vulnerability is exploitable if version is within affected range; if service is disabled, risk is significantly reduced

System is affected if RRAS is installed/enabled AND the Windows Server version/build falls below the fixed version thresholds for the respective Windows Server 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.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 the relevant Windows security update when available. If RRAS is not required, disable the service. Implement network segmentation to limit exposure and monitor for indicators of compromise.

Recommended fix High confidence

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

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update by running 'ms-settings:windowsupdate' or check Microsoft Update Catalog
  3. Search for the security update corresponding to CVE-2025-49657 (May 2025 security updates)
  4. Apply the relevant cumulative update for your Windows Server version
  5. Restart the server if prompted by the update installation
  6. Verify the RRAS service is running normally after restart
Caveat Standard cumulative updateapply risks apply - test in staging first; RRAS configuration should be preserved but verify VPN/remote access functionality after update

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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