GHSA-FVV5-H29G-F6W5

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

• lakeFS RBAC

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. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action.
2. fs:ReadObject and fs:WriteObject enabled for some path.
3. 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.

GHSA-FVV5-H29G-F6W5 has a CVSS score of 5.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.12.1); upgrading removes the vulnerable code path.

Kodem intelligence

Releases >= 1.12.1 fix this issue in lakeFS.

1. What is GHSA-FVV5-H29G-F6W5? GHSA-FVV5-H29G-F6W5 is a medium-severity security vulnerability in github.com/treeverse/lakefs (go), affecting versions >= 0.90.0, <= 1.12.0. It is fixed in 1.12.1.
2. How severe is GHSA-FVV5-H29G-F6W5? GHSA-FVV5-H29G-F6W5 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/treeverse/lakefs are affected by GHSA-FVV5-H29G-F6W5? github.com/treeverse/lakefs (go) versions >= 0.90.0, <= 1.12.0 is affected.
4. Is there a fix for GHSA-FVV5-H29G-F6W5? Yes. GHSA-FVV5-H29G-F6W5 is fixed in 1.12.1. Upgrade to this version or later.
5. Is GHSA-FVV5-H29G-F6W5 exploitable, and should I be worried? Whether GHSA-FVV5-H29G-F6W5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-FVV5-H29G-F6W5 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-FVV5-H29G-F6W5? Upgrade github.com/treeverse/lakefs to 1.12.1 or later.