CVE-2024-43784: Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion
Impact Existing lakeFS users who have issued credentials to users who have been deleted. Creating a new user with the same username, that user will inherit all of the previous user's credentials lakeFS needs to delete user credentials upon user deletion.
Published Nov 26, 2024
Affected packages
github.com/treeverse/lakefs
- Ecosystem
- Go
- Affected
- < 1.33.0
- Fixed in
- 1.33.0
- Check
go list -m github.com/treeverse/lakefs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Existing lakeFS users who have issued credentials to users who have been deleted. Creating a new user with the same username, that user will inherit all of the previous user's credentials lakeFS needs to delete user credentials upon user deletion.
Patches
_Has the problem been patched? What versions should users upgrade to?_
Workarounds
A possible workaround will be not to reuse usernames that were previously deleted
References
_Are there any links users can visit to find out more?_
Credited to N-o-Z.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-26187
lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access
high8.1Feb 13, 2026CVE-2025-68671
lakeFS is Missing Timestamp Validation in S3 Gateway Authentication
medium6.5Jan 15, 2026CVE-2025-64179
lakeFS affected by unauthenticated access to API usage metrics
medium5.3Nov 3, 2025CVE-2025-27100
lakeFS allows an authenticated user to cause a crash by exhausting server memory
medium6.5Feb 21, 2025GHSA-fvv5-h29g-f6w5
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
medium5.3Feb 22, 2024
