CVE-2026-56297

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-08) is not newer than that change (2026-07-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FreeRDP before 3.22.0 contains a use-after-free vulnerability in dvcman_channel_close and dvcman_call_on_receive due to improper synchronization of channel_callback access. A malicious RDP server can trigger a race condition by sending DYNVC_DATA and DYNVC_CLOSE messages concurrently, causing heap-use-after-free in the drdynvc client thread and potentially enabling remote code execution or denial of service.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available. Sources: github.
Web page

FreeRDP - Use-After-Free via Race Condition in DRDYNVC Channel Callback | Advisories | VulnCheck

https://www.vulncheck.com/advisories/freerdp-use-after-free-via-race-condition-in-drdynvc-channel-callback
GitHub advisoryMentions a patch (unverified)

Use After Free and Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in FreeRDP · Advisory · FreeRDP/FreeRDP · GitHub

https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-3mv2-5q57-2v8h

Vendor Advisories for CVE-2026-56297(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuwinpr3-utils (3.30.0+dfsg-0ubuntu0.26.04.1) @ resolute2026-10-17ubuntu

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 rangeFix by version rangeDependents
freerdp22.10.0+dfsg1-1 ... 2.9.0+dfsg1-1~bpo11+1 (32 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
freerdp22.10.0+dfsg1-1 ... 2.11.7+dfsg1-6~deb12u1 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
freerdp33.15.0+dfsg-2.1 ... 3.32.1+dfsg-1~bpo13+1 (49 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
freerdp33.15.0+dfsg-2.1 ... 3.22.0+dfsg-1~bpo13+1 (17 versions)
  • every version up to 3.22.0+dfsg-1: fixed in 3.22.0+dfsg-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 311 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 211 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56297?
CVE-2026-56297 is a high-severity vulnerability; its CVE record was published on July 8, 2026. FreeRDP before 3.22.0 contains a use-after-free vulnerability in dvcmanchannelclose and dvcmancallonreceive due to improper synchronization of channelcallback access. A malicious RDP server can trigger a race condition by sending DYNVCDATA and DYNVCCLOSE messages concurrently, causing…
When was CVE-2026-56297 made public?
CVE-2026-56297 was made public on May 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-56297 actively exploited?
CVE-2026-56297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56297?
CVE-2026-56297 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-56297?
A fix for CVE-2026-56297 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56297 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56297?

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

Book a Demo →Browse All CVEs