Skip to main content
Vulnerability Database/CVE-2026-111880

CVE-2026-111880: FreeRDP Buffer Overflow Vulnerability

CVE-2026-111880 is a heap buffer overflow flaw in FreeRDP that allows unauthenticated attackers to write beyond memory allocations. This post explains its technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111880 Overview

CVE-2026-111880 is a heap out-of-bounds write [CWE-787] affecting FreeRDP versions 2.0.0 through 3.32.0. The vulnerability resides in the server-side NTLM hash-callback path, which fails to validate the Message Integrity Code (MIC) offset in AUTHENTICATE_MESSAGE structures. An unauthenticated attacker can send a crafted message containing a backward session-key offset and MIC offset. This causes the server to write 16 zero bytes beyond the allocated buffer. The flaw impacts any RDP server that uses FreeRDP as its NTLM implementation.

Critical Impact

Unauthenticated network attackers can trigger a heap out-of-bounds write on FreeRDP-based servers, enabling potential memory corruption, denial of service, and possible code execution.

Affected Products

  • FreeRDP versions 2.0.0 through 3.31.x
  • Server applications linking FreeRDP's NTLM server implementation
  • Downstream distributions bundling vulnerable FreeRDP releases

Discovery Timeline

  • 2026-10-17 - CVE-2026-111880 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-111880

Vulnerability Analysis

The vulnerability resides in FreeRDP's server-side NTLM authentication handler, specifically the hash-callback path that processes incoming AUTHENTICATE_MESSAGE structures. During NTLM authentication, the server parses offset fields that reference variable-length payloads, including the encrypted session key and the Message Integrity Code (MIC).

FreeRDP fails to validate that the MIC offset falls within the expected bounds of the allocated message buffer. When combined with a backward session-key offset, the server computes a destination pointer that lies outside the allocation. The subsequent write operation copies 16 zero bytes to that out-of-bounds location, corrupting adjacent heap memory.

Root Cause

The root cause is missing bounds validation on attacker-controlled offset fields in the NTLM AUTHENTICATE_MESSAGE. The server trusts the MIC offset without verifying it points within the message payload. Backward or oversized offsets bypass implicit length checks and resolve to arbitrary heap addresses relative to the parsing buffer.

Attack Vector

Exploitation requires network access to an RDP server that uses FreeRDP for NTLM authentication. The attacker establishes an RDP connection and advances through CredSSP/NLA negotiation to the NTLM AUTHENTICATE_MESSAGE stage. No prior credentials or user interaction are required. The crafted message supplies a backward SessionKey offset paired with a MIC offset that resolves outside the allocation. On receipt, the server writes 16 zero bytes to the computed location, corrupting heap metadata or adjacent objects.

Technical details for the parsing flaw are documented in the FreeRDP GitHub Security Advisory GHSA-cmgx-558f-vh67 and the VulnCheck Advisory for FreeRDP.

Detection Methods for CVE-2026-111880

Indicators of Compromise

  • Unexpected RDP server process crashes or heap corruption aborts following inbound NLA negotiation
  • Inbound TCP 3389 connections from untrusted sources reaching NTLM AUTHENTICATE_MESSAGE without completing authentication
  • Repeated malformed CredSSP/NLA sessions from a single source IP

Detection Strategies

  • Inspect RDP/NLA traffic for AUTHENTICATE_MESSAGE structures where the MIC or EncryptedRandomSessionKey offset fields point outside the message length
  • Monitor FreeRDP server processes for abnormal termination, SIGSEGV, or glibc malloc_consolidate abort messages shortly after inbound RDP sessions
  • Deploy IDS signatures that flag NTLM messages with offset values smaller than the fixed AUTHENTICATE_MESSAGE header length

Monitoring Recommendations

  • Centralize FreeRDP server logs and crash reports to detect repeat exploitation attempts
  • Alert on inbound RDP connections to hosts not expected to expose port 3389 externally
  • Track outbound connections from RDP server processes post-session, which may indicate successful memory corruption and code execution

How to Mitigate CVE-2026-111880

Immediate Actions Required

  • Upgrade FreeRDP to version 3.32.0 or later on all server deployments
  • Audit downstream products and container images for bundled FreeRDP libraries and apply vendor-supplied updates
  • Restrict exposure of RDP services to trusted networks or VPN segments until patches are applied

Patch Information

FreeRDP version 3.32.0 adds bounds validation on the MIC and session-key offsets in the NTLM AUTHENTICATE_MESSAGE parser. Refer to the FreeRDP GitHub Security Advisory GHSA-cmgx-558f-vh67 for commit references and release notes.

Workarounds

  • Block inbound TCP 3389 at the perimeter firewall for hosts that do not require public RDP access
  • Place RDP endpoints behind an authenticated gateway or jump host that terminates NLA before FreeRDP processes it
  • Disable NTLM fallback where feasible and require Kerberos authentication for RDP sessions
bash
# Example: restrict RDP exposure with iptables until patched
iptables -A INPUT -p tcp --dport 3389 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 3389 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.