Skip to main content
VulnerabilityPublished Updated

CVE-2026-109676: FreeRDP · Use After Free

Affects FreeRDPSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 3.32.0 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.32.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Oct 2026

  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 2 Nov 2026.

What to do

Upgrade freerdp/FreeRDP to 3.32.0.

Affected software

ProductAffectedFixed in
GitHubfreerdp/FreeRDPpkg:github/freerdp/FreeRDPOther threatsAffected
  • <3.32.0
Fixed in
  • 3.32.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the affected versions are prior to 3.32.0, upgrading to version 3.32.0 or later (if available) is recommended once confirmed by the vendor. Until then, monitor vendor advisories for official fixes. No cloud service remediation applies as FreeRDP is not a cloud service.

Description

FreeRDP versions from 3.0.0-beta1 up to but not including 3.32.0 contain a use-after-free vulnerability in the smartcard handling component. This flaw allows attackers to trigger an invalid smartcard connect operation that reuses a freed smartcard handle object, potentially causing memory corruption or application crashes.

References

Community reviews

Loading reviews…