dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49681

MEDIUM · 6.5 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 →
72/100
Remediation priority · Elevated
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
Out-of-bounds read in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information 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

An out-of-bounds read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated remote attacker to read memory contents beyond allocated buffer boundaries, potentially exposing sensitive information from the server's memory.

MitigationApply the Microsoft security update for CVE-2025-49681 when released. If RRAS is not required, consider disabling 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 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build number (e.g., 10.0.14393.8246)
    Affected if The build number is below any of these thresholds: 10.0.14393.8246 (Server 2016), 10.0.17763.7558 (Server 2019), 10.0.20348.3932 (Server 2022), 10.0.25398.1732 (Server 2022 23h2), 10.0.26100.4652 (Server 2025), or if running Server 2008/2012 (any build)
  2. Verify RRAS is installed on the system
    Run 'Get-WindowsFeature -Name *Routing*' in PowerShell, or check for the presence of the 'RemoteAccess' service via 'Get-Service | Where-Object {$_.Name -eq "RemoteAccess"}'
    Affected if The RemoteAccess (RRAS) Windows feature is installed or the RemoteAccess service exists on the system
  3. Confirm RRAS service is enabled or running
    Run 'Get-Service RemoteAccess' to check the service status; also check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess' to see if the service is configured
    Affected if The RemoteAccess service is present, enabled, or running (even if currently stopped, the binary is still vulnerable if the version is unpatched)
  4. Identify the specific Windows Server edition
    Run 'systeminfo' or check 'winrm id' output to confirm whether the system is Standard, Datacenter, or a specific variant like Server 2022 23h2
    Affected if The system is an affected edition (Standard, Datacenter, etc.) running a vulnerable build as determined in step 1

The system is vulnerable if it is any version of Windows Server 2008/2012, or a later Server version with a build number lower than the patched thresholds AND has the RRAS/RemoteAccess component installed, regardless of whether the service is currently running.

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 Microsoft security update for CVE-2025-49681 when released. If RRAS is not required, consider disabling the service to reduce attack surface.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2025-49681 via Windows Update (check MSRC for the specific KB article)

  1. Open Windows Update on the affected server
  2. Check for available security updates
  3. Install the relevant cumulative update for your Windows Server version that addresses CVE-2025-49681
  4. Restart the server if prompted
  5. Verify the RRAS service is running correctly after restart
  6. Confirm the installed build number matches or exceeds the fixed version for your server (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)

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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