External risk intelligence

FreeRDP Heap-Based Buffer Overflow Denial of Service

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-64620

FreeRDP is a core component used to implement Remote Desktop Protocol (RDP) services. RDP gateways and servers are frequently exposed directly to the internet to facilitate remote access, and this vulnerability is reachable pre-authentication, making it highly likely to be encountered in internet-facing RDP deployment scenarios.

Buffer Overflow

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in FreeRDP, a component used for Remote Desktop Protocol services. This issue, a heap-based buffer overflow, allows an unauthenticated attacker to cause a denial of service by sending a specially crafted message during the security handshake. Given that RDP services are often exposed to the internet, this vulnerability presents a significant risk to organizations utilizing FreeRDP.

  • Flaw allows attackers to crash systems remotely.
  • Affects internet-facing remote access services.
  • Confirm relevance and assess exposure risk.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could target a server running FreeRDP by sending specially crafted network traffic. The vulnerability lies in how the server handles encrypted client random data during the RDP Standard Security handshake. By exploiting a flaw in the RSA decryption process, an attacker can cause a buffer overflow, potentially leading to a denial of service.

  • No authentication required.
  • Triggered during security handshake.
  • Denial of service risk.

Live Threat

Current exploitation, exposure, and threat context

A heap-based buffer overflow in the RSA decryption process could allow an unauthenticated attacker to cause a denial of service on the server. This occurs when a client selects RDP Standard Security and the server processes the encrypted client random, as the decryption result can exceed a fixed buffer size.

  • Server availability.
  • Unauthenticated network access.
  • Service disruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for RDP infrastructure, application delivery, and security operations should prioritize addressing this vulnerability. The immediate first step is to inventory all systems utilizing FreeRDP, determine their exposure to the network, and identify the system owners accountable for remediation. Planning should then focus on risk-based mitigation, considering the criticality of affected services and the availability of maintenance windows for applying updates or implementing compensating controls.

  • RDP and infrastructure teams own remediation.
  • Verify external RDP exposure and business criticality.
  • Plan and coordinate vendor updates or mitigation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is FreeRDP?

FreeRDP is an open-source software suite that implements the Remote Desktop Protocol (RDP). Developers and organizations use it to provide remote connectivity services, allowing users to interact with desktop environments over a network. It acts as a foundational library for many RDP-based clients and server implementations, enabling remote access to Windows and Linux systems.

How does CVE-2026-64620 work?

This vulnerability is a heap-based buffer overflow (CWE-122). It occurs in the RSA decryption process within the library. When the software decrypts specific incoming data, it fails to check if the result fits into the allocated memory before writing it. This allows an attacker to write excessive data past the end of the intended buffer, which destabilizes the service.

Do I need to authenticate to trigger this?

No, authentication is not required. The flaw is triggered during the early RDP Standard Security handshake phase before the server verifies the user. This means any network-connected system running an affected version can be targeted. If a client does not use RDP Standard Security, or if the connection process does not reach the specific vulnerable decryption step, this bug is not triggered.

Why is this a high priority for my team?

According to Halo Surface Signal, this vulnerability is critical because FreeRDP is often used for RDP gateways and servers that are directly exposed to the internet. Since the flaw is reachable pre-authentication, any system accessible from the internet is a potential target for a service-disrupting attack, making it highly relevant for teams managing remote access infrastructure.

What should I do to address this?

Start by identifying all systems in your environment that rely on FreeRDP versions 3.27.1 or older. Once you have a complete inventory, verify which of those systems are reachable from the internet. Coordinate with the relevant infrastructure or system owners to plan a patch cycle. If a patch cannot be applied immediately, investigate network-level controls to restrict access to those services until they are updated.

References