CVE Tools

CVE-2026-54995

Windows Reliable Multicast Transport Driver (RMCAST) Remote Code Execution Vulnerability

No known exploitation. EPSS puts it in the 54th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Identify which machines run the affected Windows versions: Windows 10, Windows 11, or the listed Windows Server editions.
  2. Check whether each machine has been updated past the “fixed in” versions for its specific edition (see below).
  3. Install the Microsoft update for CVE-2026-54995 on each affected machine and confirm the update is installed.
  4. If you can’t update immediately, temporarily limit exposure of those machines to untrusted networks until the update is applied.

What it is

From the CVE record

Use after free in Reliable Multicast Transport Driver (RMCAST) allows an unauthorized attacker to execute code over a network.

In plain language

Written by AI from the record

CVE-2026-54995 is a Windows network flaw that can let a remote attacker run code, without needing a login or clicking anything. Because it’s a serious remote code execution risk, most small businesses should act to update their affected Windows systems.

CVE-2026-54995 is a remote code execution issue in the Windows Reliable Multicast Transport Driver (RMCAST) caused by a use-after-free memory flaw that can be triggered over the network without authentication or user interaction.

If you're affected

  • Full system compromise
  • Malware installation risk
  • Service disruption
  • Possible ransomware deployment

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS54th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.8% chance of exploitation activity in the next 30 days, which ranks it in the 54th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 6 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Record updated
  4. Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 Version 1607, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store