Homepage

Incorrect Authorization Affecting weed-volume package, versions <4.40-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.38% (30th percentile)

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-19502757
  • published3 Sept 2026
  • disclosed26 Aug 2026
Report a new vulnerability Found a mistake?

Introduced: 26 Aug 2026

CVE-2026-77611  (opens in a new tab)
CWE-863  (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 versions prior to 4.40, an authenticated S3 principal with permissions scoped to a nested object key can overwrite a different object outside that scope by calling PutObjectAcl on the key it is allowed to access. The handler authorizes the request against the requested nested key but then writes the updated entry back to the bucket root rather than the key's actual parent directory, so an ACL change on allowed/protected.txt is instead applied to protected.txt at the bucket root. Because the update carries the full entry rather than only ACL metadata, an existing target object is overwritten with the content, metadata, owner information, and ACL of the scoped object, bypassing the object-level action scoping configured through the static S3 identity file. This issue is fixed in version 4.40.