This page was not yet optimized for use on mobile devices.
CVE-2026-64621
Data
| Vulnerability ID | CVE-2026-64621 |
|---|---|
| Published on | 20.07.2026 12:19 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:freerdp:freerdp:3.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.0.0:beta2:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.0.0:beta3:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.0.0:beta4:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.0.0:rc0:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.1.0:*:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.2.0:*:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.3.0:*:*:*:*:*:*:*,
cpe:2.3:a:freerdp:freerdp:3.4.0:*:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.