CVE-2026-72903

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd 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
Elevated

Also known asEUVD-2026-55844 (ENISA EUVD)Source: ENISA EUVD

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

A fix is available — apply it.

Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.235, a malicious SFTP server can return a backslash traversal filename through entry.name. In tabby-ssh/src/session/sftp.ts, SFTPSession.readdir() and _makeFile() use POSIX path processing that preserves the backslashes as ordinary filename characters. In tabby-ssh/src/components/sftpPanel.component.ts, downloadFolderRecursive() propagates item.name into the local relative path. In tabby-electron/src/services/platform.service.ts, ElectronDirectoryDownload.createFile() passes that path to Windows-native path.join(), and in tabby-electron/src/sftpContextMenu.ts, EditSFTPContextMenu.edit() passes item.name to path.join() for the temporary edit path. Windows interprets the preserved backslashes and parent-directory components as traversal, allowing attacker-controlled content to be created or overwritten outside the selected download directory or temporary edit directory. This issue is fixed in version 1.0.235.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 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.5%
EPSS %ILE
42nd
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
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 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

August 10, 2026

Last Modified

October 24, 2026

Advisory Details (3)

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

v1.0.235

Patch available: Eugeny/tabby v1.0.235

https://github.com/Eugeny/tabby/releases/tag/v1.0.235
GitHub commit

commit 3a4a41431a61 (Eugeny/tabby)

Fix landed in Eugeny/tabby commit 3a4a41431a61 — awaiting tagged release

https://github.com/Eugeny/tabby/commit/3a4a41431a61d41dd51d4119e60cad9bf13c3399
GitHub advisoryMentions a patch (unverified)

Windows SFTP path traversal allows a malicious server to write files outside the selected download directory · Advisory · Eugeny/tabby · GitHub

https://github.com/Eugeny/tabby/security/advisories/GHSA-59p9-8gwf-v9v7

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 149 rows 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 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72903?
CVE-2026-72903 is a high-severity vulnerability; its CVE record was published on August 10, 2026. Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.235, a malicious SFTP server can return a backslash traversal filename through entry.name. In tabby-ssh/src/session/sftp.ts, SFTPSession.readdir() and _makeFile() use POSIX path processing that preserves the…
When was the CVE record for CVE-2026-72903 published?
The CVE record for CVE-2026-72903 was published on August 10, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-72903 actively exploited?
CVE-2026-72903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72903?
CVE-2026-72903 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72903?
A fix for CVE-2026-72903 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-72903

Explore →

Is Your Infrastructure Affected by CVE-2026-72903?

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

Book a Demo →Browse All CVEs