Skip to main content
VulnerabilityPublished Updated

CVE-2024-32039: FreeRDP · Integer Overflow or Wraparound

Affects FreeRDPSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.11.6 as a priority.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.8
EPSS
2.2% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.11.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade FreeRDP to 2.11.6.

Affected software

ProductAffectedFixed in
FreeRDP FreeRDPAffected
  • <2.11.6
Fixed in
  • 2.11.6

AI-suggested

Apply the official patches by upgrading FreeRDP to version 2.11.6 or later (or 3.5.0 or later). As a temporary mitigation, disable the /gfx options (e.g., use /bpp:32 or /rfx) to avoid triggering the vulnerability. No other vendor advisories indicate additional mitigations or that no action is required.

Description

FreeRDP versions prior to 2.11.6 and 3.5.0 contain an integer overflow vulnerability that can lead to out-of-bounds write conditions. This flaw affects FreeRDP clients using the Remote Desktop Protocol and can be triggered when using the /gfx options. The issue is patched in versions 2.11.6 and 3.5.0. As a temporary workaround, users can disable the /gfx options, for example by using /bpp:32 or /rfx.

References

Community reviews

Loading reviews…