dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33064

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 authorized 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 authenticated remote attacker to execute arbitrary code via memory corruption. The vulnerability affects the RRAS service which handles network routing, VPN, and remote access functionalities on Windows systems.

MitigationApply the Microsoft security update for CVE-2025-33064 via Windows Update or Microsoft Update Catalog. Test RRAS functionality (routing, VPN, remote access) after patching to ensure continued operation.

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 10 1507Operating system
Affected:< 10.0.10240.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 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 RRAS service exists and is in a Started or Stopped state (vulnerability only applies if RRAS is present)
  2. Confirm Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build number
    Affected if Build number falls below any of these thresholds: 10240.21034 (1507), 14393.8148 (1607), 17763.7434 (1809), 19044.5965 (21h2), 19045.5965 (22h2), 22621.5472 (11 22h2), 22631.5472 (11 23h2), 26100.4270 (11 24h2)
  3. Check if RRAS is enabled or configured
    Run 'netsh routing ip show status' or check RRAS configuration via Routing and Remote Access snap-in (rrasmgmt.msc)
    Affected if RRAS is configured with any routing or VPN functionality (even if currently stopped, presence of configuration indicates potential exposure)
  4. Verify security update installation
    Run 'wmic qfe list' or 'Get-HotFix | Where-Object {$_.Description -like "Security Update"}' and look for KB5002537 or subsequent RRAS-related security patches for CVE-2025-33064
    Affected if No corresponding security update for CVE-2025-33064 is installed and RRAS is present

Environment is affected if RRAS (Routing and Remote Access) is installed and the Windows build number is below the affected version thresholds without the CVE-2025-33064 security update applied.

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.10240.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply the Microsoft security update for CVE-2025-33064 via Windows Update or Microsoft Update Catalog. Test RRAS functionality (routing, VPN, remote access) after patching to ensure continued operation.

Recommended fix High confidence

Apply the May 2025 Windows security update (KBXXXXXXX) for your specific Windows version - the fixed builds are: Windows 10 1507 to 10.0.10240.21034, Windows 10 1607 to 10.0.14393.8148, Windows 10 1809 to 10.0.17763.7434, Windows 10 21h2 to 10.0.19044.5965, Windows 10 22h2 to 10.0.19045.5965, Window

  1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Determine which Windows 10 or 11 release channel you are on (1507, 1607, 1809, 21h2, 22h2, 11 22h2, 11 23h2, or 11 24h2)
  3. Check the installed build number against the fixed version for your release: 10.0.10240.21034 (1507), 10.0.14393.8148 (1607), 10.0.17763.7434 (1809), 10.0.19044.5965 (21h2), 10.0.19045.5965 (22h2), 10.0.22621.5472 (11 22h2), 10.0.22631.5472 (11 23h2), or 10.0.26100.4270 (11 24h2)
  4. If below the fixed version, apply the May 2025 Windows security update via Windows Update or download from Microsoft Update Catalog
  5. Restart the system as prompted after the update is applied
  6. Verify the fix by checking the build number matches or exceeds the fixed version for your release
Caveat No significant breaking changes expected - this is a security patch for RRAS; ensure to back up critical data before any system update as standard practice

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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