CVE-2026-111880: FreeRDP heap out-of-bounds write in NTLM hash-callback

CVE-2026-111880 · Severity: high · CVSS 7.4 · Published 2026-10-17

FreeRDP is a remote desktop protocol implementation used for connecting to and controlling Windows systems. Unauthenticated attackers can exploit a flaw in NTLM authentication to write data beyond allocated memory on FreeRDP servers configured with NTLM hash callbacks, potentially leading to memory corruption and denial of service.

Technologies: FreeRDP Project FreeRDP. Vendors: FreeRDP Project.

Quick answers

Is CVE-2026-111880 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-111880 being exploited in the wild.
How severe is CVE-2026-111880?
High severity, with a CVSS score of 7.4, published 17 October 2026.
Which products and versions are affected?
FreeRDP Project FreeRDP 2.0.0 to 3.31.1.
Is there a fix for CVE-2026-111880?
Yes: fixed in 3.32.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-111880 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-111880?
Check whether you run FreeRDP Project FreeRDP at an affected version. 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.

How to fix

  • Fixed in: 3.32.0

Technical details

The vulnerability exists in ntlm_computeMicValue in ntlm.c, where the message integrity check (MIC) offset is not validated to ensure it stays within the authenticate message buffer bounds. An unauthenticated RDP client can send a crafted AUTHENTICATE_MESSAGE with a backward session-key offset (at position 0) and an out-of-bounds MIC offset to trigger a 16-byte zero write beyond the allocated buffer. The attack only affects servers with SspiNtlmHashCallback configured and does not bypass authentication itself, but can corrupt heap metadata and potentially enable further exploitation.

Affected products

  • FreeRDP Project FreeRDP 2.0.0 to 3.31.1

Timeline

  • 2026-10-02: disclosed
  • 2026-10-17: advisory

References

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