No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 01 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:freerdp:freerdp:*:*:*:*:*:*:*:* |
Mon, 01 Jun 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 29 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Freerdp
Freerdp freerdp |
|
| Vendors & Products |
Freerdp
Freerdp freerdp |
Fri, 29 May 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.26.0, FreeRDP's RDPEAR NDR parser accepts one non-null NDR pointer ref-id for multiple logical pointer fields without tracking the pointed object's expected NDR type or ownership. When the same ref-id is reused across two pointer fields, the parser assigns the same heap object to both output fields. The generic destructor later walks each field independently and destroys/frees both pointers. This causes a malicious-server-triggerable heap use-after-free / double-free in the FreeRDP client's RDPEAR authentication-redirection path. This vulnerability is fixed in 3.26.0. | |
| Title | FreeRDP RDPEAR NDR ref-id aliasing causes client-side UAF/double-free and type confusion | |
| Weaknesses | CWE-415 CWE-416 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-02T03:55:50.692Z
Reserved: 2026-05-06T14:40:00.953Z
Link: CVE-2026-44422
Updated: 2026-06-01T15:16:22.858Z
Status : Analyzed
Published: 2026-05-29T20:16:24.660
Modified: 2026-06-01T17:26:33.080
Link: CVE-2026-44422
No data.
OpenCVE Enrichment
Updated: 2026-05-29T21:30:06Z