Unauthenticated code execution via RPC out-of-bounds write
Published Sep 8, 2026 · Updated Sep 10, 2026
Out-of-bounds write in Microsoft Windows RPC Runtime allows remote attackers to execute arbitrary code through network RPC traffic. Microsoft has not disclosed the RPC parsing routine, malformed field, or bounds-check failure that causes the out-of-bounds write. No authentication or user interaction is required, and successful exploitation executes code on the affected Windows host.
Summary
What happened
Out-of-bounds write in Microsoft Windows RPC Runtime allows remote attackers to execute arbitrary code through network RPC traffic. Microsoft has not disclosed the RPC parsing routine, malformed field, or bounds-check failure that causes the out-of-bounds write. No authentication or user interaction is required, and successful exploitation executes code on the affected Windows host.
The record
- CVE
- CVE-2026-69819
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-787, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.9245
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