CVE-2026-109250: FreeRDP 3.0.0 before 3.32.0 Heap Buffer Overflow via PKCS#11 collect_keys()

Published Oct 12, 2026
·
Updated

FreeRDP 3.0.0 before 3.32.0 contains a heap buffer overflow vulnerability in collectkeys() that allows local attackers to write past the fixed 64-entry keys array during PKCS#11 key enumeration. Attackers controlling smartcard tokens can present more than 64 public key objects across multiple slots to corrupt heap memory with attacker-chosen CKAID and CKALABEL data during smartcard logon.

Affected Software

7 affected componentsFixes available
FreeRDP freerdp>=3.0.0<3.32.0
FreeRDP freerdp>=3.0.0<3.32.0
debian/freerdp2*
debian/freerdp3*
debian/freerdp3<3.32.0+dfsg-1
3.32.0+dfsg-1
debian/freerdp2<=2.11.7+dfsg1-6~deb12u1
debian/freerdp3<=3.15.0+dfsg-2.1+deb13u3
3.32.2+dfsg-13.33.0+dfsg-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/freerdp3 to a version that resolves this vulnerability.

    Fixed in 3.32.0+dfsg-1
  2. Upgrade

    Upgrade debian/freerdp3 to a version that resolves this vulnerability.

    Fixed in 3.32.2+dfsg-1Fixed in 3.33.0+dfsg-1
  3. Upgrade

    Upgrade FreeRDP to a version that resolves this vulnerability.

    Fixed in 3.32.0

Event History

Oct 12, 2026
CVE Published
via MITRE·04:04 PM
Data Sourced
via MITRE·04:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·05:17 PM
Affected Software

Frequently Asked Questions

1

Who is exposed to this issue?

FreeRDP installations running versions 3.0.0 before 3.32.0 are exposed when they use PKCS#11 smartcard logon and enumerate keys from a token controlled by an attacker.

2

What does an attacker need to exploit it?

The attacker needs control of a smartcard token presented during smartcard logon. The token must expose more than 64 public-key objects across multiple slots, with attacker-controlled CKA_ID and CKA_LABEL data.

3

Are systems using FreeRDP without PKCS#11 smartcard logon affected through this path?

The described overflow occurs during PKCS#11 key enumeration for smartcard logon. The provided information does not identify another affected path.

4

What can be done if upgrading is not immediately possible?

Avoid using attacker-controlled smartcard tokens for PKCS#11 smartcard logon, particularly tokens that may expose large numbers of public-key objects. Upgrade to FreeRDP 3.32.0 or later when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203