Answer in brief
CVE-2026-44422 records a High severity (CVSS 7.5) vulnerability in FreeRDP RDPEAR NDR ref-id aliasing causes client-side UAF/double-free and type confusion. The current sources do not mark it as known exploited. The current feed maps FreeRDP/FreeRDP (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps FreeRDP/FreeRDP (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| FreeRDP/FreeRDPgeneric | <3.26.0 | 3.26.0 |
Published upstream
May 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.