GHSA-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
Impact A bug in permissions validation allows a user with the ci:ReadAction permission to skip read checks when copying an object. If they additionally have read and write permission to path in the repository, they can copy an otherwise unreadable object and read it. In order to be affected and exploitable, the following conditions must ALL occur on the same user: 1. ci:ReadAction enabled for the repository.
Published Feb 22, 2024
Affected packages
github.com/treeverse/lakefs
- Ecosystem
- Go
- Affected
- >= 0.90.0, <= 1.12.0
- Fixed in
- 1.12.1
- Check
go list -m github.com/treeverse/lakefs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A bug in permissions validation allows a user with the ci:ReadAction permission to skip read checks when copying an object. If they additionally have read and write permission to path in the repository, they can copy an otherwise unreadable object and read it.
In order to be affected and exploitable, the following conditions must ALL occur on the same user:
ci:ReadActionenabled for the repository. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action.fs:ReadObjectandfs:WriteObjectenabled for some path.fs:ReadObject_not_ available for some path
Such a user can use (1) to copy the unreadable object (3) to a path that they can read and write (2). At that point they can read the object copy.
Patches
Releases >= 1.12.1 fix this issue in lakeFS.
Workarounds
As a workaround, use RBAC to deny ci:* permissions to all users, or to all users who have limited read access.
Many installations are unaffected:
- Installations using ACLs are _not_ affected. This includes all OSS installations that have not implemented an external authorization server. We do not know of any OSS installations that have implemented such a server. ACLs that allow ci:ReadAction also allow reading repositories, so no capabilities are granted.
- **Installations using RBAC that use only predefined policies with "all" ARNs ("*") are _not_ affected. This includes all installations that have not defined any new groups in RBAC.**
In order to be affected, installations using RBAC must define users and simultaneous allow ci:ReadAction and disallow fs:ReadObject for some path. ci:ReadAction is available in policies RepoManagementReadAll and RepoManagementFullAccess. By default these actions are configured for groups Developers and above, for all repositories and paths.
References
Credited to arielshaqed.
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, 2025CVE-2024-43784
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion
medium5.7Nov 26, 2024
