Unauthenticated code execution via RPC heap overflow
Published Aug 11, 2026 · Updated Aug 25, 2026
Heap-based buffer overflow in Microsoft Windows RPC Runtime allows remote attackers to execute code via crafted network traffic. The published record identifies RPC Runtime as the affected locus but does not disclose the malformed field or missing bounds check. No authentication or user interaction is required, and successful exploitation runs attacker-controlled code in the vulnerable service's security context.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows RPC Runtime allows remote attackers to execute code via crafted network traffic. The published record identifies RPC Runtime as the affected locus but does not disclose the malformed field or missing bounds check. No authentication or user interaction is required, and successful exploitation runs attacker-controlled code in the vulnerable service's security context.
The record
- CVE
- CVE-2026-62781
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.9121
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo