User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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. 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. 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…

Published by the source

22 Feb 2024, 21:36 UTC

Last modified by the source

22 Feb 2024, 21:36 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fvv5-h29g-f6w5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-fvv5-h29g-f6w5

Advisory: User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
IDs: GHSA-fvv5-h29g-f6w5
Record: https://patchnext.com/advisories/ghsa-fvv5-h29g-f6w5 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/treeverse/lakefs 1.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/treeverse/lakefs: affected >= 0.90.0, <= 1.12.0; fixed in 1.12.1

## Suggested inspection (read-only)
- Go github.com/treeverse/lakefs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/treeverse/lakefs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fvv5-h29g-f6w5 (GitHub-reviewed advisory GHSA-fvv5-h29g-f6w5 lists affected ranges: Go github.com/treeverse/lakefs >=0.90.0 <=1.12.0)

Commands are suggestions: review each one before running it.