CVE-2026-72921
JWT path-scope bug in SeaweedFS allows cross-tenant access prior to 4.24.
Is CVE-2026-72921 being exploited?
Not confirmed. CVE-2026-72921 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-72921?
CVE-2026-72921 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72921?
Yes. A fix has been recorded for CVE-2026-72921. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72921 affect?
CVE-2026-72921 affects SeaweedFS < 4.24 (filer component, /weed/server/filer_server_handlers.go). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72921?
Upgrade to SeaweedFS 4.24; rotate scoped tokens and audit access logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated scoped JWT can read and write other tenants' paths due to improper prefix check, enabling data exposure and modification.
Patch when possible
- affected< 4.24
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.