CVE-2026-91957

LOWPre-NVD 3.13.1
EchelonGraph scoreHIGH confidence

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

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-09-15. A secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
3.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

FreeRDP before 3.31.0 contains a use-after-free vulnerability in the smartcard RDPDR device handler when worker thread creation fails after device registration. Attackers can trigger thread creation failure during channel setup to cause device pointer deallocation while devman retains a reference, leading to crash or code execution.

CVSS v3
3.1
EG Score
3.1LOWhigh confidence
EG Risk
14
EG Risk 14/100

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 (value × EchelonGraph’s weight)
Severity31% × 45%
The EG Score, 3.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.4%
EPSS %ILE
27th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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

September 15, 2026

Last Modified

September 24, 2026

References (2)

Vendor Advisories for CVE-2026-91957(1)

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

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.32.0+dfsg-1 (47 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
freerdp33.15.0+dfsg-2.1 ... 3.30.0+dfsg-1~bpo13+1 (40 versions)
  • every version up to 3.31.0+dfsg-1: fixed in 3.31.0+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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. 1 repeat row among the latest 54 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-12 14:45 UTCEG score recompute
  4. 2026-10-11 19:36 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  5. 2026-10-11 19:13 UTCEG score recompute
  6. 2026-10-11 16:29 UTCEG score recompute
  7. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-11 13:44 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-08 22:38 UTCEG score recompute
  12. 2026-10-08 22:38 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  13. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-06 00:11 UTCEG score recompute
  17. 2026-10-06 00:11 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  18. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-03 03:13 UTCEG score recompute
  21. 2026-10-03 03:13 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  22. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-09-30 06:15 UTCEG score recompute
  25. 2026-09-30 06:15 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
Show 28 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  3. 2026-09-27 09:17 UTCEG score recompute
  4. 2026-09-27 09:17 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-09-24 12:18 UTCEG score recompute
  8. 2026-09-24 12:18 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-09-23 09:26 UTCEG score recompute
  11. 2026-09-23 09:26 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  12. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-09-20 12:28 UTCEG score recompute
  16. 2026-09-20 12:28 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  19. 2026-09-17 15:24 UTCEG score recompute
  20. 2026-09-17 15:24 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  21. 2026-09-17 15:04 UTCEG score recompute
  22. 2026-09-17 15:04 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  23. 2026-09-16 21:07 UTCEG score recompute
  24. 2026-09-16 21:07 UTCGHSA enrichmentGHSA-h5f5-2qh4-2xjm · GitHub severity LOW · GitHub CVSS 3.1
  25. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-09-15 16:33 UTCEG score recompute
  27. 2026-09-15 15:23 UTCEG score recomputeFirst assessed: 3.1 LOW
  28. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-91957?
CVE-2026-91957 is a low-severity vulnerability; its CVE record was published on September 15, 2026. FreeRDP before 3.31.0 contains a use-after-free vulnerability in the smartcard RDPDR device handler when worker thread creation fails after device registration. Attackers can trigger thread creation failure during channel setup to cause device pointer deallocation while devman retains a reference,…
When was CVE-2026-91957 made public?
CVE-2026-91957 was made public on August 31, 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 September 15, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-91957 actively exploited?
CVE-2026-91957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91957?
CVE-2026-91957 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91957?
A fix for CVE-2026-91957 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-91957 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-91957

Explore →

Is Your Infrastructure Affected by CVE-2026-91957?

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

Book a Demo →Browse All CVEs