CVE-2026-77317

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

The CVE record names the fixed release — apply it.

SeaweedFS is a distributed storage system for files and blobs. In versions from 3.88 through 4.39, the SFTP server evaluates configured path permissions with a literal string-prefix comparison, so a user scoped to a path is also granted the same access to any sibling path whose name merely begins with the same characters. A user granted access to /tenants/alice therefore also matches /tenants/alice-archive, /tenants/alice2, and similar siblings, because the check does not require a path-component boundary. An authenticated low-privilege SFTP user with a root home directory and narrow path permissions can thereby cross the configured ACL boundary to read another tenant's files, and to overwrite them if granted write, all through the documented SFTP service with its own valid credentials. This issue is fixed in version 4.40.

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 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)
Severity81% × 45%
The EG Score, 8.1 of 10.
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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. 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 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 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit 29981f8d24a6 (seaweedfs/seaweedfs)

Fix landed in seaweedfs/seaweedfs commit 29981f8d24a6 — awaiting tagged release

https://github.com/seaweedfs/seaweedfs/commit/29981f8d24a62e9571962c4534fb23c48c00bae2
GitHub advisoryMentions a patch (unverified)

SFTP path ACL literal prefix match permits cross-tenant file read and overwrite · Advisory · seaweedfs/seaweedfs · GitHub

https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-fvpg-g364-j8vh

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 57× 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. 2 repeat rows among the latest 93 are merged into the row they repeat.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77317?
CVE-2026-77317 is a high-severity vulnerability; its CVE record was published on August 26, 2026. SeaweedFS is a distributed storage system for files and blobs. In versions from 3.88 through 4.39, the SFTP server evaluates configured path permissions with a literal string-prefix comparison, so a user scoped to a path is also granted the same access to any sibling path whose name merely begins…
When was the CVE record for CVE-2026-77317 published?
The CVE record for CVE-2026-77317 was published on August 26, 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-77317 actively exploited?
CVE-2026-77317 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77317?
CVE-2026-77317 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-77317?
The CVE record for CVE-2026-77317 names the fix: "This issue is fixed in version 4.40."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-77317?

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

Book a Demo →Browse All CVEs