CVE-2026-109250
Freerdp 3.0.0 – 3.32.0
Raw vector
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-109250 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Freerdp. Its CVSS base score is 7.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-97694
Vulnerability Data
FreeRDP 3.0.0 before 3.32.0 contains a heap buffer overflow vulnerability in collect_keys() 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…
more
across multiple slots to corrupt heap memory with attacker-chosen CKA_ID and CKA_LABEL data during smartcard logon.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.
Training developers on secure coding practices (input validation, bounds checking) reduces instances of improper array index validation, but is fallible — developers can still write code with missing or incorrect bounds checks even after training, leaving a substantial remainder.
Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.
A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase software weaknesses like CWE-129 in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
A.8.8's reach is DISCLOSURE — it sees array-index validation errors only where they have been published as CVEs or vendor advisories, and most CWE-129 instances in first-party code never surface that way; the observed CVEs show the class does get disclosed, so the found share is a minority rather than zero.