The CVE describes a heap-based buffer overflow in rasapi32.dll (Remote Access API), rated CVSS 7.8 as a local privilege escalation. Read that literally and you get the wrong threat model. rasapi32.dll is a legacy component dating to Windows 2000 era, and it loads during network initialization—often before user session establishment—in the context of services that hold elevated privileges specifically to manage VPN tunnels, dial-up connections, and DirectAccess. The 'authorized attacker' qualifier in the disclosure does not mean this requires console access; it means the attacker needs valid credentials on a domain-joined machine, which is a lateral movement threshold, not a post-exploitation one. The 'authorized attacker' buffer has been used before in Microsoft CVEs (CVE-2015-0057, CVE-2016-0041) to similar effect—it creates CVSS breathing room that real-world attack chains don't respect. What makes this worse: rasapi32.dll doesn't just run elevated. It touches credential stores, DNS configuration, and routing tables. Exploiting this gives SYSTEM plus direct control over the machine's network identity. That's not privilege escalation—that's infrastructure compromise in a single chain. DNS hijacking becomes possible. Routing table manipulation bypasses segmentation. Credential stores expose plaintext without hash cracking. The CVSS 7.8 doesn't model any of this because it stops at the privilege boundary. On the 2026 dating: this either indicates a forward-dated coordinated disclosure with an embargo period, or it's a historical vulnerability being retroactively documented. If the latter, the vulnerable code path may have existed for years in deprecated interfaces that stopped getting security review. Either way, patch latency is the real enemy here—not because the fix is complex, but because RAS components persist in enterprise environments where no one is actively monitoring them, precisely because the 'authorized attacker' framing let this sit below urgent scanner thresholds. If you maintain systems with DirectAccess, legacy VPN clients, or any RAS-dependent third-party wrappers, prioritize this patch. The attack surface isn't just the DLL—it's every tool that consumes RAS APIs and cannot be updated independently.
CVE-2026-65672
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 Remote Access API allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 analysisData overflows a buffer allocated on the heap, corrupting neighbouring heap structures and allocator metadata that a patient attacker can groom into control of execution. It is subtler than a stack overflow but just as dangerous. The fix is validating lengths before every write and using safe allocators and bounded operations.
General guidance for the heap-based buffer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 10.0.22631.7517< 10.0.26000.9106< 10.0.26100.9106< 10.0.28000.2704< 10.0.20348.5440< 10.0.26100.33222CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
From vendor data10.0.20348.544010.0.22631.751710.0.26000.9106
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-65672 — 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 sourcesThe CVE describes a heap-based buffer overflow in rasapi32.dll (Remote Access API), rated CVSS 7.8 as a local privilege escalation. Read that literally and you get the wrong threat model. rasapi32.dll is a legacy component dating to Windows 2000 era, and it loads during network initialization—often before user session establishment—in the context of services that hold elevated privileges specifically to manage VPN tunnels, dial-up connections, and DirectAccess. The 'authorized attacker' qualifier in the disclosure does not mean this requires console access; it means the attacker needs valid credentials on a domain-joined machine, which is a lateral movement threshold, not a post-exploitation one. The 'authorized attacker' buffer has been used before in Microsoft CVEs (CVE-2015-0057, CVE-2016-0041) to similar effect—it creates CVSS breathing room that real-world attack chains don't respect. What makes this worse: rasapi32.dll doesn't just run elevated. It touches credential stores, DNS configuration, and routing tables. Exploiting this gives SYSTEM plus direct control over the machine's network identity. That's not privilege escalation—that's infrastructure compromise in a single chain. DNS hijacking becomes possible. Routing table manipulation bypasses segmentation. Credential stores expose plaintext without hash cracking. The CVSS 7.8 doesn't model any of this because it stops at the privilege boundary. On the 2026 dating: this either indicates a forward-dated coordinated disclosure with an embargo period, or it's a historical vulnerability being retroactively documented. If the latter, the vulnerable code path may have existed for years in deprecated interfaces that stopped getting security review. Either way, patch latency is the real enemy here—not because the fix is complex, but because RAS components persist in enterprise environments where no one is actively monitoring them, precisely because the 'authorized attacker' framing let this sit below urgent scanner thresholds. If you maintain systems with DirectAccess, legacy VPN clients, or any RAS-dependent third-party wrappers, prioritize this patch. The attack surface isn't just the DLL—it's every tool that consumes RAS APIs and cannot be updated independently.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-65672 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
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