CVE-2025-49674
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 · uneditedHeap-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 confidenceA heap-based buffer overflow vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated attacker on the network to execute arbitrary code. The vulnerability stems from improper memory handling within the RRAS service component, which can be triggered by sending specially crafted network packets to the affected system.
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 dataall versions= r2all versions= r2< 10.0.14393.8246< 10.0.17763.7558< 10.0.20348.3932< 10.0.25398.1732< 10.0.26100.4652CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify RRAS service statusOpen Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell. Check if the RemoteAccess service is running or set to start.Affected if RRAS (RemoteAccess) is enabled or running - the vulnerability only affects systems with RRAS active
-
Check Windows Server build versionRun 'winver' from command prompt or 'Get-ComputerInfo | Select-Object OsBuildNumber,OsVersion' in PowerShell. Note the full build number (e.g., 10.0.14393.8246).Affected if Build number falls below the fixed versions: Server 2016 < 14393.8246, 2019 < 17763.7558, 2022 < 20348.3932, 2022 23h2 < 25398.1732, 2025 < 26100.4652. Server 2008/2012/R2 all versions are affected.
-
Check for security update installationRun 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' or check Windows Update history for recent RRAS-related security patches.Affected if No recent security update matching CVE-2025-49674 has been installed (specific patch KB number from Microsoft advisory)
-
Verify RRAS role or feature is installedRun 'Get-WindowsFeature RemoteAccess' or check Server Manager for Routing and Remote Access role installation status.Affected if Routing and Remote Access role/feature is installed on the server
System is affected if RRAS (RemoteAccess service) is enabled AND the Windows Server build version is below the fixed thresholds for the respective version, or if the CVE-2025-49674 security update has not been applied.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.824610.0.17763.755810.0.20348.3932
Apply Microsoft security updates for Windows RRAS when released; if patches are unavailable, consider disabling RRAS if not required or implementing network segmentation to limit exposure to untrusted networks.
Windows Server 2016: build 10.0.14393.8246+ | Windows Server 2019: build 10.0.17763.7558+ | Windows Server 2022: build 10.0.20348.3932+ | Windows Server 2022 23h2: build 10.0.25398.1732+ | Windows Server 2025: build 10.0.26100.4652+
- Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- Determine if the server is running a supported version (2016, 2019, 2022, 2022 23h2, or 2025)
- For Windows Server 2016: Upgrade to build 10.0.14393.8246 or later
- For Windows Server 2019: Upgrade to build 10.0.17763.7558 or later
- For Windows Server 2022: Upgrade to build 10.0.20348.3932 or later
- For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1732 or later
- For Windows Server 2025: Upgrade to build 10.0.26100.4652 or later
- Apply the update via Windows Update, WSUS, or download the specific update from Microsoft Update Catalog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49674 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49674 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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