Authorization Bypass Through User-Controlled Key Affecting weed-volume package, versions <4.40-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-WEEDVOLUME-19504516
- published3 Sept 2026
- disclosed26 Aug 2026
Introduced: 26 Aug 2026
CVE-2026-77368 (opens in a new tab)How to fix?
Upgrade Minimos:latest weed-volume to version 4.40-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream weed-volume package and not the weed-volume package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.
References
- https://www.cve.org/CVERecord?id=CVE-2026-77368
- https://osv.dev/vulnerability/MINI-2xqh-mc9j-qm78
- https://osv.dev/vulnerability/CVE-2026-77368
- https://github.com/seaweedfs/seaweedfs/commit/ce82e3a057080162a9fba11889157d2255815f71
- https://github.com/seaweedfs/seaweedfs/commit/fa549e9c83b7799d512157d728f52052912831af
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-99q7-x53r-6j4g