dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49671

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
Exposure of sensitive information to an unauthorized actor 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

Windows Routing and Remote Access Service (RRAS) contains a vulnerability that allows an unauthorized attacker on the network to access sensitive information. This is an information disclosure flaw in a Windows networking service that handles remote access and routing functionality.

MitigationApply the relevant Microsoft security update for RRAS when available, and restrict network access to RRAS to trusted internal networks only.

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. Identify Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows Server build number
    Affected if Version is Windows Server 2008/2012 (any build), 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, or Server 2025 < 10.0.26100.4652
  2. Verify RRAS role is installed
    Run 'Get-WindowsFeature -Name Routing' in PowerShell (requires RSAT) or check via Server Manager > Add Roles and Features > Remote Access (Routing role)
    Affected if The Routing role or role service appears installed in the list of installed features
  3. Confirm RRAS service status
    Run 'Get-Service -Name RemoteAccess' or check service status in services.msc for 'Routing and Remote Access' (RRAS) service
    Affected if The RemoteAccess service is installed and shows a status other than 'Not Installed' or disabled
  4. Check network exposure of RRAS
    Run 'netsh routing ip show interfaces' or inspect RRAS configuration in Routing and Remote Access snap-in (rrasmgmt.msc) to determine which network interfaces are listening
    Affected if RRAS is bound to network adapters accessible from untrusted networks (not restricted to localhost or internal management VLANs)

You are affected if your Windows Server version falls within the affected build ranges AND the RRAS role is installed and accessible on your network.

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 Microsoft security update for RRAS when available, and restrict network access to RRAS to trusted internal networks only.

Recommended fix High confidence

Windows Server 2016 (10.0.14393.8246+), Windows Server 2019 (10.0.17763.7558+), Windows Server 2022 (10.0.20348.3932+), Windows Server 2022 23h2 (10.0.25398.1732+), Windows Server 2025 (10.0.26100.4652+)

  1. Backup critical data and document current RRAS configuration before updating
  2. Apply the latest Windows security update for your server version from Windows Update or Microsoft Update Catalog
  3. For Windows Server 2016: update to version 10.0.14393.8246 or later
  4. For Windows Server 2019: update to version 10.0.17763.7558 or later
  5. For Windows Server 2022: update to version 10.0.20348.3932 or later
  6. For Windows Server 2022 23h2: update to version 10.0.25398.1732 or later
  7. For Windows Server 2025: update to version 10.0.26100.4652 or later
  8. Restart the server if prompted by the update installation
Caveat Security updates typically have minimal impact; verify RRAS routing and remote access policies 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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