Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 21 Jan 2026 03:45:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 15 Jan 2026 21:15:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Thu, 15 Jan 2026 17:15:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freerdp
Freerdp freerdp |
|
| Vendors & Products |
Freerdp
Freerdp freerdp |
Thu, 15 Jan 2026 07:15:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 15 Jan 2026 03:00:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.20.1, global-buffer-overflow was observed in FreeRDP's Base64 decoding path. The root cause appears to be implementation-defined char signedness: on Arm/AArch64 builds, plain char is treated as unsigned, so the guard c <= 0 can be optimized into a simple c != 0 check. As a result, non-ASCII bytes (e.g., 0x80-0xFF) may bypass the intended range restriction and be used as an index into a global lookup table, causing out-of-bounds access. This vulnerability is fixed in 3.20.1. | |
| Title | FreeRDP has a global-buffer-overflow in crypto_base64_decode | |
| Weaknesses | CWE-125 CWE-758 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-01-14T21:12:03.734Z
Reserved: 2026-01-12T16:20:16.746Z
Link: CVE-2026-22858
Updated: 2026-01-14T21:12:00.311Z
Status : Analyzed
Published: 2026-01-14T18:16:43.520
Modified: 2026-01-20T18:33:32.850
Link: CVE-2026-22858
OpenCVE Enrichment
Updated: 2026-01-15T17:03:21Z