Quick answers
- Is CVE-2026-111376 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111376 being exploited in the wild.
- How severe is CVE-2026-111376?
- Medium severity, with a CVSS score of 5, published 16 October 2026.
- Which products and versions are affected?
- FreeRDP Project FreeRDP 3.30.0 through 3.31.1.
- Is there a fix for CVE-2026-111376?
- 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-111376 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111376?
- 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 Windows cliprdr handler in CliprdrStream_New dereferences an eight-byte buffer (LONGLONG) without validating that the server's response contains at least eight bytes. When a malicious RDP server responds to a FILECONTENTS_SIZE request with fewer than eight bytes (e.g., 1, 2, or 4 bytes), the code reads beyond the allocated heap buffer's boundary. This requires user interaction (pasting or opening a remote clipboard file) and a network connection to the attacker-controlled RDP server; no authentication bypass or code execution is established.
Affected products
- FreeRDP Project FreeRDP 3.30.0 through 3.31.1
Timeline
- 2026-10-01: disclosed
- 2026-10-16: advisory