CVE-2026-88219: Microsoft RPC Runtime untrusted pointer dereference

CVE-2026-88219 · Severity: high · CVSS 8.8 · Published 2026-10-13

A vulnerability in Microsoft's RPC (Remote Procedure Call) Runtime component allows an attacker on the network to remotely execute code without authentication. This could enable an attacker to compromise systems running the affected RPC Runtime, leading to full system compromise, data theft, or deployment of malware.

Technologies: Microsoft RPC Runtime. Vendors: Microsoft.

Quick answers

Is CVE-2026-88219 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-88219 being exploited in the wild.
How severe is CVE-2026-88219?
High severity, with a CVSS score of 8.8, published 13 October 2026.
Which products and versions are affected?
Microsoft RPC Runtime.
Is there a fix for CVE-2026-88219?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-88219 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-2026-88219?
Check whether you run Microsoft RPC Runtime. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an untrusted pointer dereference in the RPC Runtime component that can be triggered over the network by an unauthenticated attacker. By sending a crafted network request to trigger the unsafe pointer dereference, an attacker can achieve remote code execution. The attack requires network access but no prior authentication or user interaction.

Affected products

  • Microsoft RPC Runtime

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.