CVE-2026-121952

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-116952 (ENISA EUVD) · GHSA-9gqr-m6pm-p7q7 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FreeRDP before 3.32.2 has an out-of-bounds write in the proxy because rdp_read_bitmap_cache_v2_capability_set rejects only numCellCaches values above 5, yet the bitmap cache v2 cell array is later accessed at fixed indices 0 through 4. A client connecting to the proxy can declare fewer than five cell caches in its Confirm Active, causing heap corruption, heap data leakage to the backend, or a crash.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
75
EG Risk 75/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

Advisory Details (2)

Auto-updated Nov 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

FreeRDP proxy out-of-bounds write in bitmap cache v2 capability handling · Advisory · FreeRDP/FreeRDP · GitHub

https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-xc85-4mqc-xgcx
Web page

FreeRDP before 3.32.2 Proxy Out-of-Bounds Write via Bitmap Cache v2 Capability | Advisories | VulnCheck

https://www.vulncheck.com/advisories/freerdp-before-3.32.2-proxy-out-of-bounds-write-via-bitmap-cache-v2-capability

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatfreerdp-2:3.32.2-1.el10_32026-11-11redhat
redhatfreerdp-2:3.32.2-1.el10_22026-11-03redhat

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

(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(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 24× 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.5% · 43rd percentile
  2. 2026-11-13 03:21 UTCEchelonGraph re-scored
  3. 2026-11-13 03:21 UTCVendor advisory
  4. 2026-11-13 03:21 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-12 03:01 UTCEchelonGraph re-scored
  7. 2026-11-12 03:01 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-11 02:41 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-10 21:35 UTCEchelonGraph re-scored
  11. 2026-11-10 21:35 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-09 21:09 UTCEchelonGraph re-scored
  14. 2026-11-09 21:09 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-08 20:49 UTCEchelonGraph re-scored
  17. 2026-11-08 20:49 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-11-07 20:28 UTCEchelonGraph re-scored
  20. 2026-11-07 20:28 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-11-06 20:08 UTCEchelonGraph re-scored
  23. 2026-11-06 20:08 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-11-06 00:25 UTCOSV refresh
Show 11 more
  1. 2026-11-05 19:46 UTCEchelonGraph re-scored
  2. 2026-11-05 19:46 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-04 19:26 UTCEchelonGraph re-scored
  5. 2026-11-04 19:26 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-04 18:46 UTCEchelonGraph re-scored
  7. 2026-11-04 18:46 UTCGHSA enrichmentGHSA-9gqr-m6pm-p7q7 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-11-04 17:03 UTCENISA EUVD ID recordedEUVD-2026-116952 · Source: ENISA EUVD
  9. 2026-11-04 16:27 UTCEchelonGraph re-scored
  10. 2026-11-04 15:41 UTCEchelonGraph re-scoredFirst assessed: 9.8 CRITICAL
  11. 2026-11-04 15:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-121952?
CVE-2026-121952 is a critical-severity vulnerability; its CVE record was published on November 4, 2026. FreeRDP before 3.32.2 has an out-of-bounds write in the proxy because rdp_read_bitmap_cache_v2_capability_set rejects only numCellCaches values above 5, yet the bitmap cache v2 cell array is later accessed at fixed indices 0 through 4. A client connecting to the proxy can declare fewer than five…
When was CVE-2026-121952 made public?
CVE-2026-121952 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-121952 actively exploited?
CVE-2026-121952 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-121952?
CVE-2026-121952 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-121952?
A fix for CVE-2026-121952 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-121952 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-121952

Explore →

Is Your Infrastructure Affected by CVE-2026-121952?

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