CVE-2026-111382 FreeRDP CVE debrief

Who should care

Defenders responsible for FreeRDP clients, particularly those using versions before 3.32.0, should assess exposure and prioritize remediation. This includes IT teams managing client systems, security teams monitoring for potential threats, and operators responsible for maintaining system integrity. They should verify client version and update to 3.32.0 or later to prevent potential code execution.

Why it matters

CVE-2026-111382 is a high-severity vulnerability in FreeRDP before 3.32.0, allowing malicious RDP servers to corrupt client memory. Defenders should assess exposure, prioritize remediation, and verify client version to prevent potential code execution.

• Potential code execution on client-side
• Heap corruption and memory manipulation
• Requires verification of client version and exposure
• Remediation priority for FreeRDP clients before 3.32.0

Technical summary

The vulnerability exists in the general_LumaToYUV444 and general_ChromaV2ToYUV444 functions of FreeRDP before 3.32.0. Malicious RDP servers can send RDPGFX AVC444 or AVC444v2 frames with odd-height region rects ending at surface height to write past U/V planes, enabling heap corruption and potential code execution. Defenders should focus on verifying client versions and assessing exposure to prevent potential code execution. This client-side vulnerability requires immediate attention from defenders responsible for FreeRDP clients.

Defensive priority

High

Recommended defensive actions

• Assess exposure by checking client version
• Prioritize remediation for clients using FreeRDP before 3.32.0
• Verify client version and update to 3.32.0 or later
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, specific information on affected versions, exploitation, and remediation is limited. Defenders should verify client version and assess exposure. The CVE record was published on 2026-10-16T03:18:05.400Z and has not been modified since then. Additional details may be found in the official CVE Program record and NIST NVD detail page.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.