Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:XSummary
CVE-2026-24679 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Freerdp Freerdp. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-24679 is a high-severity vulnerability (CVSS 9.1) affecting FreeRDP, an open-source implementation of the Remote Desktop Protocol, in versions prior to 3.22.0. The issue resides in the URBDRC client, which processes USB Redirection Channel data and uses server-supplied interface numbers directly as array indices without performing bounds checks. This leads to an out-of-bounds read in the libusb_udev_select_interface function, classified under CWE-122 (Heap-based Buffer Overflow).
Remote attackers can exploit this vulnerability over the network with low complexity, requiring no privileges, no user interaction, and no special setup on the target. By crafting malicious RDP traffic with oversized or invalid interface numbers, an attacker connecting to a vulnerable FreeRDP client can trigger the out-of-bounds read, potentially resulting in sensitive memory disclosure (high confidentiality impact) or application crash and denial of service (high availability impact), while integrity remains unaffected.
The FreeRDP security advisory (GHSA-2jp4-67x6-gv7x) and the fixing commit (2d563a50be17c1b407ca448b1321378c0726dd31) confirm the vulnerability was addressed in version 3.22.0 by adding proper bounds validation on the server-supplied interface numbers before indexing the array. Security practitioners should prioritize updating FreeRDP clients to 3.22.0 or later to mitigate this risk.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6486
Vulnerability Data
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.22.0, The URBDRC client uses server-supplied interface numbers as array indices without bounds checks, causing an out-of-bounds read in libusb_udev_select_interface. This vulnerability is fixed in 3.22.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.
Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.
Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.
Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.
Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.