dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-49729

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 via specially crafted network requests to the RRAS service, which listens on the network.

MitigationApply Microsoft security updates for CVE-2025-49729 when released; if RRAS is not required, disable the service to eliminate the 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
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 is installed
    Open Server Manager > Add Roles and Features > check if 'Remote Access' role with 'Routing' role service is installed, or run: Get-WindowsFeature -Name RemoteAccess
    Affected if RRAS role is installed on the server
  2. Check RRAS service status
    Open Services.msc and locate 'Routing and Remote Access' service, or run: Get-Service RemoteAccess
    Affected if The RemoteAccess service is running (status = 'Running')
  3. Confirm RRAS is listening on network
    Run netstat -an | findstr ':1723' or check for listening ports associated with RRAS (PPTP port 1723, GRE protocol 47)
    Affected if RRAS is listening on any network interface (not loopback only)
  4. Identify Windows Server version
    Run winver, or: [System.Environment]::OSVersion.Version, or check systeminfo | findstr /C:"OS Version"
    Affected if Version falls within affected ranges: Server 2008/2012 (all), 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
  5. Verify security update is NOT installed
    Run: Get-HotFix | Where-Object {$_.Description -match 'Security Update'} or check Windows Update history for CVE-2025-49729
    Affected if The specific security patch for CVE-2025-49729 is not installed

Server is affected if RRAS is installed, running, listening on network, and the Windows version is below the fixed builds AND the CVE-2025-49729 security update is not installed.

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 CVE-2025-49729 when released; if RRAS is not required, disable the service to eliminate the attack surface.

Recommended fix High confidence

Apply Microsoft security update for CVE-2025-49729 (build numbers: 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)

  1. Check current Windows Server build version by running 'winver' or 'systeminfo' in command prompt
  2. Open Windows Update or check Microsoft Update Catalog for the latest security updates
  3. Search for and install the Microsoft security update corresponding to CVE-2025-49729 (may be part of a monthly cumulative update)
  4. Restart the server if prompted by the update installation
  5. Verify the build number matches or exceeds the fixed version threshold for your Windows Server version
  6. If RRAS is not needed, consider disabling the Routing and Remote Access Service to reduce attack surface using 'netsh routing ip disbled' or through Services console
Caveat Standard patching risks apply - test updates in staging environment before production deployment; some updates may require service restart

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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