dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33066

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 →
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 attacker to execute arbitrary code remotely by sending specially crafted network packets to the RRAS service.

MitigationApply Microsoft security updates for this vulnerability immediately; if RRAS is not required, disable the service; restrict network access to RRAS servers and follow least-privilege principles.

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
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 feature installation status
    Run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell (Windows Server) or check 'Programs and Features > Windows Features' for 'Routing and Remote Access' on Windows 10/11
    Affected if The RemoteAccess feature is installed or the RRAS service exists on the system
  2. Confirm RRAS service is running
    Run 'Get-Service RemoteAccess' or check the status of the 'Routing and Remote Access' service in Services.msc
    Affected if The RemoteAccess service is running or set to start automatically
  3. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the exact OS build number (e.g., 19045.5965)
    Affected if The installed build number is lower than any of the following: 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 (22h2), 10.0.22631.5472 (23h2), or 10.0.26100.4270 (24h2)
  4. Verify RRAS network listener presence
    Run 'netsh routing ip show interfaces' or check open ports via 'netstat -an | findstr ":1723"' (PPTP) or port 47 (GRE) to see if RRAS is actively listening
    Affected if RRAS interfaces are active and listening on network ports

The system is affected if RRAS is installed/running on a Windows version with a build number below the thresholds listed above, exposing the buffer overflow vulnerability to network attackers.

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 Microsoft security updates for this vulnerability immediately; if RRAS is not required, disable the service; restrict network access to RRAS servers and follow least-privilege principles.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21034 | Windows 10 1607: 10.0.14393.8148 | Windows 10 1809: 10.0.17763.7434 | Windows 10 21h2: 10.0.19044.5965 | Windows 10 22h2: 10.0.19045.5965 | Windows 11 22h2: 10.0.22621.5472 | Windows 11 23h2: 10.0.22631.5472 | Windows 11 24h2: 10.0.26100.4270

  1. Identify current Windows version by running 'winver' or 'systeminfo' command
  2. Determine which version branch your system is on (e.g., 1507, 1607, 1809, 21h2, 22h2, or 11 22h2/23h2/24h2)
  3. Apply the appropriate Windows security update from Windows Update or Microsoft Update Catalog for your specific version
  4. Restart the system after the update is installed
  5. Verify the installed version matches or exceeds the fixed build number for your version branch
  6. Ensure RRAS service is running and test remote access functionality
Caveat Standard Windows cumulative update applies; test RRAS configuration and any VPN/remote access workflows in staging before production deployment

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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