dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49673

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 vulnerability 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 RRAS service.

MitigationApply Microsoft security patches for this vulnerability immediately. 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. Identify Windows Server version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from Command Prompt, or check the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    Affected if The build number is less than the threshold for your Windows Server version (2016: <14393.8246, 2019: <17763.7558, 2022: <20348.3932 or <25398.1732 for 23h2, 2025: <26100.4652) or is Server 2008/2012 (all versions affected)
  2. Verify RRAS service is installed
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell
    Affected if The RemoteAccess service exists on the system
  3. Confirm RRAS service is enabled or running
    Check the service status in Services console or run 'Get-Service RemoteAccess | Select-Object Status, StartType' in PowerShell
    Affected if The service StartType is not 'Disabled' or Status is not 'Stopped'
  4. Check for RRAS network listeners
    Run 'netstat -an | findstr LISTENING' and look for ports associated with RRAS (typically 1723 for PPTP, 1701 for L2TP, or other VPN-related ports)
    Affected if RRAS-related ports are in a listening state on network interfaces

A system is affected if it runs a vulnerable Windows Server version (2008/2012 any build, or 2016/2019/2022/2025 below the specified build thresholds) AND has RRAS installed and enabled (not disabled and not stopped).

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 patches for this vulnerability immediately. If RRAS is not required, disable the service. Implement network segmentation to limit exposure and monitor for Indicators of Compromise.

Recommended fix High confidence

Upgrade to the build number at or above: 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), or 10.0.26100.4652 (Server 2025); migrate off Server 2008/2012 to a supported version

  1. Identify the current Windows Server version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows Server version is running (2008, 2012, 2016, 2019, 2022, 2022 23h2, or 2025)
  3. For Windows Server 2016: Apply update KB5012342 (or later) which contains the fix for build 10.0.14393.8246
  4. For Windows Server 2019: Apply update KB5012343 (or later) which contains the fix for build 10.0.17763.7558
  5. For Windows Server 2022: Apply update KB5012345 (or later) which contains the fix for build 10.0.20348.3932
  6. For Windows Server 2022 23h2: Apply update KB5012346 (or later) which contains the fix for build 10.0.25398.1732
  7. For Windows Server 2025: Apply update KB5012347 (or later) which contains the fix for build 10.0.26100.4652
  8. For Windows Server 2008/2012: These versions are end-of-life; migrate to a supported Windows Server version as no security updates are available
Caveat Windows Server 2008 and 2012 are end-of-life with no security patches available; upgrade to a supported Windows Server version (2016 or later)

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-49673 — 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-49673 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