CVE-2026-44420

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 3.7%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.26.0, a malicious RDP client can trigger a heap-buffer-overflow write in FreeRDP's server-side clipboard (cliprdr) channel by sending a CB_CLIP_CAPS PDU with a too-small capabilitySetLength. This can crash the server process (remote DoS) and may be exploitable for code execution because it corrupts heap memory. This vulnerability is fixed in 3.26.0.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
4%
EPSS %ILE
89%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 27, 2026

Advisory Details (1)

Auto-updated May 31, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

FreeRDP cliprdr server heap-buffer-overflow via undersized capabilitySetLength in CB_CLIP_CAPS · Advisory · FreeRDP/FreeRDP · GitHub

https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-mvpx-xj7r-3p3r

Vendor Advisories for CVE-2026-44420(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuwinpr3-utils (3.30.0+dfsg-0ubuntu0.26.04.1) @ resolute2026-08-25ubuntu
redhatfreerdp-2:3.10.3-3.el10_0.92026-07-27redhat
redhatfreerdp-2:3.10.3-12.el10_2.62026-07-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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.26.0+dfsg-1~bpo13+1 (32 versions)3.26.0+dfsg-1

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 65× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:17 UTCEG score recompute
  11. 2026-08-25 04:17 UTCVendor advisory
  12. 2026-08-23 14:11 UTCEG score recompute
  13. 2026-08-23 14:11 UTCVendor advisory
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 14:59 UTCEG score recompute
  17. 2026-08-21 14:59 UTCVendor advisory
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 21:56 UTCVendor advisory
  20. 2026-08-20 10:24 UTCEG score recompute
  21. 2026-08-20 10:24 UTCVendor advisory
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 06:51 UTCEG score recompute
Show 75 more
  1. 2026-08-17 06:51 UTCVendor advisory
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 06:13 UTCEG score recompute
  4. 2026-08-16 06:13 UTCVendor advisory
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 18:41 UTCEG score recompute
  7. 2026-08-15 18:41 UTCVendor advisory
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 23:28 UTCVendor advisory
  10. 2026-08-14 11:57 UTCVendor advisory
  11. 2026-08-14 00:27 UTCEG score recompute
  12. 2026-08-14 00:27 UTCVendor advisory
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 09:39 UTCVendor advisory
  15. 2026-08-12 22:08 UTCEG score recompute
  16. 2026-08-12 22:08 UTCVendor advisory
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-12 10:38 UTCVendor advisory
  19. 2026-08-11 22:51 UTCEG score recompute
  20. 2026-08-11 22:51 UTCVendor advisory
  21. 2026-08-11 13:43 UTCEPSS rescore
  22. 2026-08-11 11:13 UTCEG score recompute
  23. 2026-08-11 11:13 UTCVendor advisory
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 23:43 UTCVendor advisory
  26. 2026-08-10 04:34 UTCVendor advisory
  27. 2026-08-09 17:03 UTCEG score recompute
  28. 2026-08-09 17:03 UTCVendor advisory
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 05:33 UTCVendor advisory
  31. 2026-08-08 18:03 UTCEG score recompute
  32. 2026-08-08 18:03 UTCVendor advisory
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 06:17 UTCVendor advisory
  35. 2026-08-07 18:47 UTCEG score recompute
  36. 2026-08-07 18:47 UTCVendor advisory
  37. 2026-08-07 07:16 UTCVendor advisory
  38. 2026-08-06 19:46 UTCEG score recompute
  39. 2026-08-06 19:46 UTCVendor advisory
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-06 08:15 UTCVendor advisory
  42. 2026-08-05 20:42 UTCEG score recompute
  43. 2026-08-05 20:42 UTCVendor advisory
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-04 23:05 UTCEG score recompute
  46. 2026-08-04 23:05 UTCVendor advisory
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:38 UTCEPSS rescore
  49. 2026-08-04 03:25 UTCVendor advisory
  50. 2026-08-03 15:55 UTCEG score recompute
  51. 2026-08-03 15:55 UTCVendor advisory
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-03 00:28 UTCVendor advisory
  54. 2026-08-02 12:57 UTCEG score recompute
  55. 2026-08-02 12:57 UTCVendor advisory
  56. 2026-08-02 02:27 UTCEPSS rescore
  57. 2026-08-02 01:26 UTCVendor advisory
  58. 2026-08-01 13:55 UTCEG score recompute
  59. 2026-08-01 13:55 UTCVendor advisory
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-31 19:06 UTCVendor advisory
  62. 2026-07-31 05:51 UTCEG score recompute
  63. 2026-07-31 05:51 UTCVendor advisory
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 11:48 UTCEG score recompute
  67. 2026-07-29 11:48 UTCVendor advisory
  68. 2026-07-28 15:36 UTCEPSS rescore
  69. 2026-07-28 04:02 UTCEG score recompute
  70. 2026-07-28 04:02 UTCVendor advisory
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-27 13:29 UTCEG score recompute
  73. 2026-07-27 13:29 UTCVendor advisory
  74. 2026-07-27 12:40 UTCEG score recompute
  75. 2026-07-27 12:40 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-44420?
CVE-2026-44420 is a high vulnerability published on May 29, 2026. FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.26.0, a malicious RDP client can trigger a heap-buffer-overflow write in FreeRDP's server-side clipboard (cliprdr) channel by sending a CBCLIPCAPS PDU with a too-small capabilitySetLength. This can crash the server process…
When was CVE-2026-44420 disclosed?
CVE-2026-44420 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44420 actively exploited?
CVE-2026-44420 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 11.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44420?
CVE-2026-44420 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44420?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44420, 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-44420

Explore →

Is Your Infrastructure Affected by CVE-2026-44420?

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