cve.bz

CVE-2026-109940 freerdp freerdp: Stack-based Buffer Overflow

5.1 mediumExploit referenceEPSS 0.1%

Medium (5.1) in freerdp freerdp. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
FreeRDP 3.0.0-beta1 before 3.32.0 on Unix builds with PKCS#11 support has a stack-based buffer overflow in wprintKeyName() in WinPR's NCrypt PKCS#11 provider. It hex-encodes a key's CKA_ID, which can be up to 64 bytes, into a fixed 128-byte stack buffer. An attacker supplying a malicious PKCS#11 token or module whose key and matching certificate use a 55- to 64-byte CKA_ID can overflow the client's stack during key enumeration, causing a crash.

Severity

CVSS 4.0

5.1 medium
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

4.6 medium
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-109940 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109940?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109940?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109940 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
FreeRDPfrom 3.0.0-beta1 before 3.32.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12freerdp2no fix listedDEBIAN-CVE-2026-109940
Debian13freerdp3no fix listedDEBIAN-CVE-2026-109940
Debian14freerdp33.32.0+dfsg-1DEBIAN-CVE-2026-109940
Ubuntu16.04:LTS, 18.04:LTSfreerdpno fix listedUBUNTU-CVE-2026-109940
Ubuntu22.04:LTS, Pro:18.04:LTS, Pro:20.04:LTS and 1 morefreerdp2no fix listedUBUNTU-CVE-2026-109940
Ubuntu24.04:LTSfreerdp33.32.0+dfsg-0ubuntu0.24.04.1UBUNTU-CVE-2026-109940
Ubuntu26.04:LTSfreerdp33.32.0+dfsg-0ubuntu0.26.04.1UBUNTU-CVE-2026-109940

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated Moderate because a stack buffer overflow in the PKCS#11 key-name path can crash FreeRDP. The attack requires a local/physical token interaction model reflected in AV:P and user involvement (UI:R). Impact is availability-only.

Red Hat's mitigation

If PKCS#11 smartcard/token support is unused, disable or avoid PKCS#11 providers in FreeRDP. Restrict token use to trusted environments.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10freerdpFix deferred
Red Hat Enterprise Linux 6freerdpNot affected
Red Hat Enterprise Linux 7freerdpNot affected
Red Hat Enterprise Linux 8freerdpNot affected
Red Hat Enterprise Linux 9freerdpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-109940.

References

Check your stackJSON