CVE-2026-33985
Heap Memory Disclosure in FreeRDP Before 3.24.2 Causes Data Leak
Publication date: 2026-03-30
Last updated on: 2026-04-01
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freerdp | freerdp | to 3.24.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-131 | The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol. Prior to version 3.24.2, the software could render pixel data from adjacent heap memory to the screen. This means that data from memory areas next to the intended pixel data could be displayed, potentially exposing sensitive information to an attacker.
How can this vulnerability impact me? :
The vulnerability can lead to leakage of sensitive data because pixel data from adjacent heap memory is rendered to the screen. An attacker could exploit this to view information that should remain confidential, potentially compromising privacy or security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade FreeRDP to version 3.24.2 or later, where the issue has been patched.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in FreeRDP prior to version 3.24.2 causes pixel data from adjacent heap memory to be rendered to the screen, potentially leaking sensitive data to an attacker.
Such leakage of sensitive data could have implications for compliance with data protection standards and regulations like GDPR and HIPAA, which require protection of sensitive information from unauthorized disclosure.
However, the provided information does not explicitly discuss the impact of this vulnerability on compliance with these standards or regulations.