CVE-2026-121963

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

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

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-11-04. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-116963 (ENISA EUVD) · GHSA-xfcc-7m23-p7v6 (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
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.3%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FreeRDP before 3.32.2 contains a use-after-free vulnerability in the asynchronous dynamic rdpsnd channel that allows malicious RDP servers to trigger freed callback access by closing the channel with queued audio PDUs. Attackers can send a training PDU then close the channel so the playback thread reads the freed callback in rdpsnd_virtual_channel_write, crashing the client.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
43
EG Risk 43/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)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 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.3%
EPSS %ILE
24th
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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

November 4, 2026

Last Modified

November 5, 2026

Affected Packages

(3 across 3 ecosystems)
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.33.0+dfsg-1 (51 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
freerdp33.15.0+dfsg-2.1 ... 3.32.1+dfsg-1~bpo13+1 (46 versions)
  • every version up to 3.32.2+dfsg-1: fixed in 3.32.2+dfsg-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 14× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  4. 2026-11-11 07:26 UTCEchelonGraph re-scored
  5. 2026-11-11 07:26 UTCGHSA enrichmentGHSA-xfcc-7m23-p7v6 · GitHub severity HIGH · GitHub CVSS 5.9
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-11-05 19:28 UTCEchelonGraph re-scored
  12. 2026-11-05 19:28 UTCGHSA enrichmentGHSA-xfcc-7m23-p7v6 · GitHub severity HIGH · GitHub CVSS 5.9
  13. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  14. 2026-11-04 19:28 UTCEchelonGraph re-scored
  15. 2026-11-04 19:28 UTCGHSA enrichmentGHSA-xfcc-7m23-p7v6 · GitHub severity HIGH · GitHub CVSS 5.9
  16. 2026-11-04 18:27 UTCEchelonGraph re-scored
  17. 2026-11-04 18:26 UTCEchelonGraph re-scored
  18. 2026-11-04 17:03 UTCENISA EUVD ID recordedEUVD-2026-116963 · Source: ENISA EUVD
  19. 2026-11-04 16:27 UTCEchelonGraph re-scored
  20. 2026-11-04 15:41 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  21. 2026-11-04 15:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-121963?
CVE-2026-121963 is a medium-severity vulnerability; its CVE record was published on November 4, 2026. FreeRDP before 3.32.2 contains a use-after-free vulnerability in the asynchronous dynamic rdpsnd channel that allows malicious RDP servers to trigger freed callback access by closing the channel with queued audio PDUs. Attackers can send a training PDU then close the channel so the playback thread…
When was CVE-2026-121963 made public?
CVE-2026-121963 was made public on October 20, 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 November 4, 2026. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-121963 actively exploited?
CVE-2026-121963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-121963?
CVE-2026-121963 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-121963?
A fix for CVE-2026-121963 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-121963 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-121963

Explore →

Is Your Infrastructure Affected by CVE-2026-121963?

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