SeaweedFS is a distributed storage system for files and blobs. In version 4.39, the filer's TUS resumable-upload handler checks JWT allowed_prefixes scoping only when a session is created, letting a low-privilege tenant hijack another tenant's upload session to write content to filer paths their own token forbids. The HEAD, PATCH, and DELETE verbs that act on an existing session by its id never verify that the session's stored target path falls within the caller's allowed prefixes, so a tenant who obtains another upload's session identifier can PATCH attacker bytes into it and, on completion, have the file land at the victim's out-of-scope path. The same token can also DELETE other tenants' sessions and HEAD them to read upload progress and size, defeating the JWT prefix isolation. This vulnerability only affects deployments that configure filer JWT signing and have TUS uploads enabled. This issue is fixed in version 4.40.
CVE-2026-77368
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(medium)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
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 computedSeverity76% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (3)
Auto-updated Aug 26, 2026commit fa549e9c83b7 (seaweedfs/seaweedfs)
Fix landed in seaweedfs/seaweedfs commit fa549e9c83b7 — awaiting tagged release
https://github.com/seaweedfs/seaweedfs/commit/fa549e9c83b7799d512157d728f52052912831afcommit ce82e3a05708 (seaweedfs/seaweedfs)
Fix landed in seaweedfs/seaweedfs commit ce82e3a05708 — awaiting tagged release
https://github.com/seaweedfs/seaweedfs/commit/ce82e3a057080162a9fba11889157d2255815f71Authenticated Cross-Prefix IDOR in SeaweedFS Filer TUS Handler Enables Arbitrary Write to Tenant-Forbidden Paths · Advisory · seaweedfs/seaweedfs · GitHub
https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-99q7-x53r-6j4gWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-27 17:30 UTCEG score recompute
- 2026-08-27 17:07 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 22:24 UTCEG score recompute
- 2026-08-26 22:02 UTCEG score recompute
- 2026-08-26 22:01 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-77368?
When was CVE-2026-77368 disclosed?
Is CVE-2026-77368 actively exploited?
What is the CVSS score of CVE-2026-77368?
How do I remediate CVE-2026-77368?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77368
Is Your Infrastructure Affected by CVE-2026-77368?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.