CVE-2026-45058

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.4Exploit: None knownExposed services: Not assessed

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

electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. In 3.8.8 and earlier, there is persistent local-pty code execution via imported bookmarks or compromised sync targets. Affects users who import bookmark JSON files or who have electerm sync configured (gist/WebDAV). The attacker can inject exec* fields or global config to cause remote code to run when a bookmark is opened or when sync is applied.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity94% × 45%
The EG Score, 9.4 of 10.
Exploitation0.3% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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

May 28, 2026

Last Modified

June 1, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Import unsafe bookmark data could lead to unsafe operations in electerm · Advisory · electerm/electerm · GitHub

https://github.com/electerm/electerm/security/advisories/GHSA-jgg9-rw32-44pj

Vendor Advisories for CVE-2026-45058(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmelecterm—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
electerm—
  • every version through 3.8.8: no fix on record
—

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 38× 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 100 of 404 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. None are among the latest 100 rows. The 304 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45058?
CVE-2026-45058 is a critical-severity vulnerability; its CVE record was published on May 28, 2026. electerm is an open-sourced terminal/ssh/sftp/telnet/serialport/RDP/VNC/Spice/ftp client. In 3.8.8 and earlier, there is persistent local-pty code execution via imported bookmarks or compromised sync targets. Affects users who import bookmark JSON files or who have electerm sync configured…
When was the CVE record for CVE-2026-45058 published?
The CVE record for CVE-2026-45058 was published on May 28, 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 June 1, 2026; the record at its source may have been updated since.
Is CVE-2026-45058 actively exploited?
CVE-2026-45058 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45058?
CVE-2026-45058 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-45058?
No fix for CVE-2026-45058 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-45058 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-45058

Explore →

Is Your Infrastructure Affected by CVE-2026-45058?

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

Book a Demo →Browse All CVEs