CVE-2026-26187: Github.com/treeverse/lakefs Path Traversal Vulnerability
HIGHCVE-2026-26187 is a HIGH (CVSS 8.1) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/treeverse/lakefs libraries in the Go ecosystem. The issue involves lakefs vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access. Remediation is available by upgrading affected packages to version 1.77.0.
CVE-2026-26187 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-26187
To remediate this vulnerability, upgrade all affected Github.com/treeverse/lakefs dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/treeverse/lakefs to 1.77.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/treeverse/lakefs
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-26187, inspect your project dependencies for Github.com/treeverse/lakefs:
inspect dependencies for github.com/treeverse/lakefs
Analyze the terminal output to locate any version of Github.com/treeverse/lakefs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.77.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/treeverse/lakefs, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-26187 Affected Github.com/treeverse/lakefs Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/treeverse/lakefs
|
Go |
< 1.77.0
|
1.77.0
|
References
Frequently Asked Questions
What is CVE-2026-26187?
Which Github.com/treeverse/lakefs versions are affected?
What version fixes CVE-2026-26187?
Is github.com/treeverse/lakefs affected?
What is the CVSS score of CVE-2026-26187?
What CWE is associated with CVE-2026-26187?
How can I check Go dependencies for CVE-2026-26187?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-699m-4v95-rmpm",
"modified" : "2026-02-13T22:11:49Z",
"published" : "2026-02-13T16:16:04Z",
"aliases" : [ "CVE-2026-26187" ],
"summary" : "lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access",
"details" : "## Summary\n\nTwo path traversal vulnerabilities in the local block adapter allow authenticated users to read and write files outside their designated storage boundaries.\n\n## Details\n\nThe local block adapter in `pkg/block/local/adapter.go` had two path traversal vulnerabilities:\n\n### 1. Prefix Bypass Vulnerability\n\nThe `verifyRelPath` function used `strings.HasPrefix()` to verify that requested paths fall within the configured storage directory. This check was insufficient because it validated only the path prefix without requiring a path separator, allowing access to sibling directories with similar names.\n\n**Example:** If the adapter is configured with base path `/data/lakefs`:\n\n| Path | Expected | Actual |\n|------|----------|--------|\n| `/data/lakefs/valid/file.txt` | Allowed | Allowed |\n| `/data/lakefs_evil/secret.txt` | Blocked | **Vulnerable** |\n| `/data/lakefs_backup/data.db` | Blocked | **Vulnerable** |\n\n### 2. Namespace Escape via Identifier\n\nThe adapter verified that resolved paths stayed within the adapter's base path, but did not verify that object identifiers stayed within their designated storage namespace. This allowed attackers to use path traversal sequences in the object identifier to access files in other namespaces.\n\n**Example:** With base path `/data/lakefs` and namespace `local://repo1/userdata`:\n\n| Identifier | Resolved Path | Expected | Actual |\n|------------|---------------|----------|--------|\n| `file.txt` | `/data/lakefs/repo1/userdata/file.txt` | Allowed | Allowed |\n| `../secrets/key.txt` | `/data/lakefs/repo1/secrets/key.txt` | Blocked | **Vulnerable** |\n| `../../other-repo/data.txt` | `/data/lakefs/other-repo/data.txt` | Blocked | **Vulnerable** |\n\nThis vulnerability allows users with access to one namespace to read and write files in other namespaces within the same lakeFS deployment.\n\n## Impact\n\nAuthenticated lakeFS users can:\n\n- **Read and write files in sibling directories** that share the same path prefix as the storage directory (vulnerability 1)\n- **Access files across namespaces** by using path traversal in object identifiers (vulnerability 2)\n\nThis could allow attackers to:\n\n- Read sensitive data from other repositories/namespaces\n- Write malicious files to other namespaces\n- Read/write files in adjacent directories outside lakeFS storage\n- Potentially escalate privileges if writable directories are used by other services\n\nThis vulnerability **only affects** deployments using the local block adapter. Deployments using S3, GCS, Azure, or other object storage backends are **not affected**.\n\n## Patches\n\nFixed in version v1.77.0.\n\nThe fixes:\n1. Append a path separator to prefix checks, ensuring paths must be within the storage directory\n2. Add two-level path validation: verify both that namespace paths stay within the adapter's base path AND that resolved paths stay within their designated namespace\n\n## Workarounds\n\n- Configure the storage path with a unique name unlikely to be a prefix of other directories\n- Restrict filesystem permissions for the lakeFS process\n- Ensure no sensitive data exists in sibling directories\n\n## Credit\n\nDiscovered via CodeQL static analysis.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/treeverse/lakefs"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.77.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.76.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/treeverse/lakeFS/security/advisories/GHSA-699m-4v95-rmpm"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-26187"
}, {
"type" : "WEB",
"url" : "https://github.com/treeverse/lakeFS/commit/cbc106275357302a834280f133265dc39f1384ce"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/treeverse/lakeFS"
}, {
"type" : "WEB",
"url" : "https://github.com/treeverse/lakeFS/releases/tag/v1.77.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-13T16:16:04Z",
"nvd_published_at" : "2026-02-13T19:17:29Z"
}
}