User with permission to write actions can impersonate another user when auth token is configured in environment variable
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact When lakeFS is configured with **ALL** of the following: - Configuration option `auth.encrypt.secret_key` passed through environment variable - Actions enabled via configuration option `actions.enabled` (default enabled) then a user who can configure an action can impersonate any other user. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds **ANY ONE** of these is sufficient to prevent the issue: * Do not pass `auth.encrypt.secret_key` through an environment variable. For instance, Kubernetes users can generate the entire configuration as a secret and mount that. This is described [here](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). * Disable actions. * Limit users allowed to configure actions.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/treeverse/lakefs (Go) | before 1.3.1 | 1.3.1 | Patch available | GHSA-26hr-q2wp-rvc5 |
- github.com/treeverse/lakefs (Go) Vendor— Affected before 1.3.1 Fixed in 1.3.1 Patch available GHSA-26hr-q2wp-rvc5
Remediation
- Fix · GHSA-26hr-q2wp-rvc5 github.com/treeverse/lakefs (Go) Fixed in 1.3.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-26hr-q2wp-rvc5
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences