CVE-2026-56297

HIGHNVD 8.17.0▼
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. NVD baseline CVSS 8.1; sources differ by 1.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

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
7.0(medium)
EPSS
20.0%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

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 Patch Available🟡 PoC Available

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 33× 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-07-13 23:53 UTCEG score recompute
  2. 2026-07-13 23:53 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 12:05 UTCEG score recompute
  5. 2026-07-13 12:05 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-13 00:17 UTCEG score recompute
  9. 2026-07-13 00:17 UTCGHSA enrichment
  10. 2026-07-12 12:29 UTCEG score recompute
  11. 2026-07-12 12:29 UTCGHSA enrichment
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-12 00:42 UTCEG score recompute
  14. 2026-07-12 00:41 UTCGHSA enrichment
  15. 2026-07-11 12:53 UTCEG score recompute
  16. 2026-07-11 12:53 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 01:06 UTCEG score recompute
  20. 2026-07-11 01:06 UTCGHSA enrichment
  21. 2026-07-10 16:18 UTCNVD updateCVSS v3 → 8.1
  22. 2026-07-10 13:17 UTCEG score recompute
  23. 2026-07-10 13:17 UTCGHSA enrichment
  24. 2026-07-10 01:29 UTCEG score recompute
  25. 2026-07-10 01:29 UTCGHSA enrichment
Show 8 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 13:41 UTCEG score recompute
  4. 2026-07-09 13:41 UTCGHSA enrichment
  5. 2026-07-09 01:53 UTCEG score recompute
  6. 2026-07-09 01:53 UTCGHSA enrichment
  7. 2026-07-08 14:06 UTCEG score recompute
  8. 2026-07-08 14:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56297?
CVE-2026-56297 is a high vulnerability 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 disclosed?
CVE-2026-56297 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56297 actively exploited?
CVE-2026-56297 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56297?
CVE-2026-56297 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.0.
How do I remediate CVE-2026-56297?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56297, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs