Summary
Workarounds
ANY ONE of these is sufficient to prevent the issue:
Do not pass
auth.encrypt.secret_keythrough an environment variable.For instance, Kubernetes users can generate the entire configuration as a secret and mount that. This is described here.
Disable actions.
Limit users allowed to configure actions.
Impact
When lakeFS is configured with ALL of the following:
- Configuration option
auth.encrypt.secret_keypassed 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.
GHSA-26HR-Q2WP-RVC5 has a CVSS score of 6.2 (Medium). The vector is network-reachable, high 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.3.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Has the problem been patched? What versions should users upgrade to?
Frequently Asked Questions
- What is GHSA-26HR-Q2WP-RVC5? GHSA-26HR-Q2WP-RVC5 is a medium-severity security vulnerability in github.com/treeverse/lakefs (go), affecting versions < 1.3.1. It is fixed in 1.3.1.
- How severe is GHSA-26HR-Q2WP-RVC5? GHSA-26HR-Q2WP-RVC5 has a CVSS score of 6.2 (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.
- Which versions of github.com/treeverse/lakefs are affected by GHSA-26HR-Q2WP-RVC5? github.com/treeverse/lakefs (go) versions < 1.3.1 is affected.
- Is there a fix for GHSA-26HR-Q2WP-RVC5? Yes. GHSA-26HR-Q2WP-RVC5 is fixed in 1.3.1. Upgrade to this version or later.
- Is GHSA-26HR-Q2WP-RVC5 exploitable, and should I be worried? Whether GHSA-26HR-Q2WP-RVC5 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
- What actually determines whether GHSA-26HR-Q2WP-RVC5 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.
- How do I fix GHSA-26HR-Q2WP-RVC5? Upgrade
github.com/treeverse/lakefsto 1.3.1 or later.