CVE-2026-67300

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

FreeRDP before 3.29.0 contains client-side heap use-after-free vulnerabilities in the async update message proxy for RAIL WINDOW_STATE_ORDER and NOTIFY_ICON_STATE_ORDER when AsyncUpdate is enabled. When a malicious or compromised RDP server sends crafted update orders, the message proxy shallow-copies structures containing nested parser-owned pointers (e.g., titleInfo.string, windowRects, visibilityRects, icon buffers). The parser frees those nested buffers after the callback returns, so the queued async message later dispatches stale pointers, potentially causing memory corruption or a client crash.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 2026

Advisory Details (3)

Auto-updated Aug 1, 2026
Patch available. Sources: github, github_commit.
generic

FreeRDP before 3.29.0 Use-After-Free via async message proxy | Advisories | VulnCheck

https://www.vulncheck.com/advisories/freerdp-before-use-after-free-via-async-message-proxy
github_commit

commit 5370fb26fbf0 (FreeRDP/FreeRDP)

Fix landed in FreeRDP/FreeRDP commit 5370fb26fbf0 — awaiting tagged release

https://github.com/FreeRDP/FreeRDP/commit/5370fb26fbf034ecd11d3026b6ad639b5fff493f
github Patch Available

FreeRDP Window and NotifyIcon async message-proxy use-after-free · Advisory · FreeRDP/FreeRDP · GitHub

https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-33gg-h66j-3697

Vendor Advisories for CVE-2026-67300(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
freerdp22.10.0+dfsg1-1 ... 2.9.0+dfsg1-1~bpo11+1 (32 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
freerdp22.10.0+dfsg1-1 ... 2.11.7+dfsg1-6~deb12u1 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
freerdp33.15.0+dfsg-2.1 ... 3.30.0+dfsg-1~bpo13+1 (43 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
freerdp33.15.0+dfsg-2.1 ... 3.28.0+dfsg-2 (37 versions)3.29.0+dfsg-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:56 UTCGHSA enrichment
  3. 2026-08-20 07:52 UTCGHSA enrichment
  4. 2026-08-19 19:51 UTCEG score recompute
  5. 2026-08-19 19:51 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:50 UTCGHSA enrichment
  8. 2026-08-18 19:47 UTCEG score recompute
  9. 2026-08-18 19:47 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:46 UTCGHSA enrichment
  12. 2026-08-17 19:39 UTCEG score recompute
  13. 2026-08-17 19:38 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 07:00 UTCGHSA enrichment
  16. 2026-08-16 19:00 UTCEG score recompute
  17. 2026-08-16 19:00 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 06:57 UTCEG score recompute
  20. 2026-08-16 06:57 UTCGHSA enrichment
  21. 2026-08-15 18:57 UTCGHSA enrichment
  22. 2026-08-15 06:56 UTCEG score recompute
  23. 2026-08-15 06:56 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 18:04 UTCGHSA enrichment
Show 55 more
  1. 2026-08-14 06:04 UTCEG score recompute
  2. 2026-08-14 06:04 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 18:03 UTCGHSA enrichment
  5. 2026-08-13 06:03 UTCGHSA enrichment
  6. 2026-08-12 18:02 UTCEG score recompute
  7. 2026-08-12 18:01 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 06:00 UTCGHSA enrichment
  10. 2026-08-11 17:59 UTCEG score recompute
  11. 2026-08-11 17:59 UTCGHSA enrichment
  12. 2026-08-11 05:58 UTCEG score recompute
  13. 2026-08-11 05:58 UTCGHSA enrichment
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 17:58 UTCGHSA enrichment
  16. 2026-08-10 05:56 UTCGHSA enrichment
  17. 2026-08-09 17:55 UTCEG score recompute
  18. 2026-08-09 17:55 UTCGHSA enrichment
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-09 05:55 UTCGHSA enrichment
  21. 2026-08-08 17:54 UTCEG score recompute
  22. 2026-08-08 17:54 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 05:53 UTCGHSA enrichment
  25. 2026-08-07 17:53 UTCEG score recompute
  26. 2026-08-07 17:53 UTCGHSA enrichment
  27. 2026-08-07 05:52 UTCGHSA enrichment
  28. 2026-08-06 17:51 UTCEG score recompute
  29. 2026-08-06 17:51 UTCGHSA enrichment
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 05:49 UTCEG score recompute
  32. 2026-08-06 05:49 UTCGHSA enrichment
  33. 2026-08-05 19:17 UTCEPSS rescore
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 17:48 UTCGHSA enrichment
  36. 2026-08-05 05:47 UTCGHSA enrichment
  37. 2026-08-04 17:46 UTCEG score recompute
  38. 2026-08-04 17:45 UTCGHSA enrichment
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:39 UTCEPSS rescore
  41. 2026-08-04 05:41 UTCGHSA enrichment
  42. 2026-08-03 17:40 UTCEG score recompute
  43. 2026-08-03 17:40 UTCGHSA enrichment
  44. 2026-08-03 16:19 UTCEG score recompute
  45. 2026-08-03 16:19 UTCGHSA enrichment
  46. 2026-08-03 13:22 UTCEG score recompute
  47. 2026-08-03 13:22 UTCGHSA enrichment
  48. 2026-08-03 10:36 UTCEPSS rescore
  49. 2026-08-03 01:21 UTCGHSA enrichment
  50. 2026-08-02 13:20 UTCGHSA enrichment
  51. 2026-08-02 01:19 UTCEG score recompute
  52. 2026-08-02 01:19 UTCGHSA enrichment
  53. 2026-08-01 13:18 UTCEG score recompute
  54. 2026-08-01 12:43 UTCEG score recompute
  55. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67300?
CVE-2026-67300 is a high vulnerability published on August 1, 2026. FreeRDP before 3.29.0 contains client-side heap use-after-free vulnerabilities in the async update message proxy for RAIL WINDOWSTATEORDER and NOTIFYICONSTATE_ORDER when AsyncUpdate is enabled. When a malicious or compromised RDP server sends crafted update orders, the message proxy shallow-copies…
When was CVE-2026-67300 disclosed?
CVE-2026-67300 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67300 actively exploited?
CVE-2026-67300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2026-67300?
CVE-2026-67300 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-67300?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67300

Explore →

Is Your Infrastructure Affected by CVE-2026-67300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs