CVE-2026-73224

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.120, electerm allows a malicious FTP or SFTP server to execute arbitrary commands when a user downloads a crafted folder and invokes Properties and Calculate Size because calcLocal in src/client/components/sftp/file-info-modal.jsx inserts the server-controlled folder name into a du -sh shell command without safely escaping single quotes. This issue is fixed in version 3.15.120.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

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 none (CISA Vulnrichment) · Automatable no (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)14 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 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

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 11, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v3.15.120

Patch available: electerm/electerm v3.15.120

https://github.com/electerm/electerm/releases/tag/v3.15.120
GitHub commit

commit 36b16fb66936 (electerm/electerm)

Fix landed in electerm/electerm commit 36b16fb66936 — awaiting tagged release

https://github.com/electerm/electerm/commit/36b16fb66936bb7c65fbcdf706dfd1b77f0750a7
GitHub advisoryMentions a patch (unverified)

Electerm check folder size function may get attacked by unsafe folder name · Advisory · electerm/electerm · GitHub

https://github.com/electerm/electerm/security/advisories/GHSA-4wx8-4m69-8rw5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 48× 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 96 of 109 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73224?
CVE-2026-73224 is a high-severity vulnerability; its CVE record was published on August 11, 2026. electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. Prior to 3.15.120, electerm allows a malicious FTP or SFTP server to execute arbitrary commands when a user downloads a crafted folder and invokes Properties and Calculate Size because calcLocal in…
When was the CVE record for CVE-2026-73224 published?
The CVE record for CVE-2026-73224 was published on August 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-73224 actively exploited?
CVE-2026-73224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73224?
CVE-2026-73224 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73224?
A fix for CVE-2026-73224 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73224

Explore →

Is Your Infrastructure Affected by CVE-2026-73224?

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

Book a Demo →Browse All CVEs