FreeRDP before 3.29.0 contains out-of-bounds read vulnerabilities in the async update message proxy for the PolygonSC and PolygonCB primary drawing orders
Affects freerdpSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 3.29.0 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.29.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade freerdp/FreeRDP to 3.29.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfreerdp/FreeRDPpkg:github/freerdp/FreeRDPOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability affects FreeRDP versions before 3.29.0, upgrading to version 3.29.0 or later is expected to address the issue once an official fix is released. Until then, avoid enabling async update mode or connecting to untrusted RDP servers with async update enabled.
Description
FreeRDP before 3.29.0 contains out-of-bounds read vulnerabilities in the async update message proxy for the PolygonSC and PolygonCB primary drawing orders. When AsyncUpdate is enabled (e.g., xfreerdp /async-update), update_message_PolygonSC() and update_message_PolygonCB() allocate a fresh points array but copy point data from the address of the order structure instead of from polygonSC->points / polygonCB->points, resulting in a client-side out-of-bounds read. A malicious or compromised RDP server sending crafted PolygonSC/PolygonCB update orders can trigger memory disclosure or a client crash.
References
- github.com/FreeRDP/FreeRDP/security/advisories/GHSA-vxp3-7g6q-rq2w (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-67301 (opens in a new tab)
- github.com/FreeRDP/FreeRDP/commit/5370fb26fbf034ecd11d3026b6ad639b5fff493f (opens in a new tab)
- vulncheck.com/advisories/freerdp-before-out-of-bounds-read-via-polygon-async-message-proxy (opens in a new tab)
- ubuntu.com/security/CVE-2026-67301 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-67301 (opens in a new tab)