Advisories
For your digest

github.com/seaweedfs/seaweedfs: SeaweedFS: Filer JWT allowed_prefixes literal prefix match allows cross-tenant access to sibling paths

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

github.com/seaweedfs/seaweedfs (Go)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • github.com/seaweedfs/seaweedfs (Go): every version, before 0.0.0-20260512171048-05ed5c9ae8a2
  • github.com/seaweedfs/seaweedfs (Go): every version, before 0.0.0-20260512171048-05ed5c9ae8a2

The fix

  • github.com/seaweedfs/seaweedfs (Go) fixed in 0.0.0-20260512171048-05ed5c9ae8a2

    go
    go get github.com/seaweedfs/seaweedfs@v0.0.0-20260512171048-05ed5c9ae8a2
    Check what is installed
    go list -m github.com/seaweedfs/seaweedfs
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/seaweedfs/seaweedfs to 0.0.0-20260512171048-05ed5c9ae8a2 or the nearest later release, to fix CVE-2026-72921. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".