CVE-2026-26187: lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access
Summary Two path traversal vulnerabilities in the local block adapter allow authenticated users to read and write files outside their designated storage boundaries. Details The local block adapter in pkg/block/local/adapter.go had two path traversal vulnerabilities: 1.
Published Feb 13, 2026
Affected packages
github.com/treeverse/lakefs
- Ecosystem
- Go
- Affected
- <= 1.76.0
- Fixed in
- 1.77.0
- Check
go list -m github.com/treeverse/lakefs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Two path traversal vulnerabilities in the local block adapter allow authenticated users to read and write files outside their designated storage boundaries.
Details
The local block adapter in pkg/block/local/adapter.go had two path traversal vulnerabilities:
1. Prefix Bypass Vulnerability
The 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.
Example: If the adapter is configured with base path /data/lakefs:
| Path | Expected | Actual | | `/data/lakefs/valid/file.txt` | Allowed | Allowed | | `/data/lakefs_evil/secret.txt` | Blocked | **Vulnerable** | | `/data/lakefs_backup/data.db` | Blocked | **Vulnerable** |
2. Namespace Escape via Identifier
The 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.
Example: With base path /data/lakefs and namespace local://repo1/userdata:
| Identifier | Resolved Path | Expected | Actual | | `file.txt` | `/data/lakefs/repo1/userdata/file.txt` | Allowed | Allowed | | `../secrets/key.txt` | `/data/lakefs/repo1/secrets/key.txt` | Blocked | **Vulnerable** | | `../../other-repo/data.txt` | `/data/lakefs/other-repo/data.txt` | Blocked | **Vulnerable** |
This vulnerability allows users with access to one namespace to read and write files in other namespaces within the same lakeFS deployment.
Impact
Authenticated lakeFS users can:
- Read and write files in sibling directories that share the same path prefix as the storage directory (vulnerability 1)
- Access files across namespaces by using path traversal in object identifiers (vulnerability 2)
This could allow attackers to:
- Read sensitive data from other repositories/namespaces
- Write malicious files to other namespaces
- Read/write files in adjacent directories outside lakeFS storage
- Potentially escalate privileges if writable directories are used by other services
This vulnerability only affects deployments using the local block adapter. Deployments using S3, GCS, Azure, or other object storage backends are not affected.
Patches
Fixed in version v1.77.0.
The fixes:
- Append a path separator to prefix checks, ensuring paths must be within the storage directory
- 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
Workarounds
- Configure the storage path with a unique name unlikely to be a prefix of other directories
- Restrict filesystem permissions for the lakeFS process
- Ensure no sensitive data exists in sibling directories
Credit
Discovered via CodeQL static analysis.
Credited to nopcoder.
References
- https://github.com/treeverse/lakeFS/security/advisories/GHSA-699m-4v95-rmpm
- https://github.com/treeverse/lakeFS/commit/cbc106275357302a834280f133265dc39f1384ce
- https://github.com/treeverse/lakeFS/releases/tag/v1.77.0
- https://nvd.nist.gov/vuln/detail/CVE-2026-26187
- https://github.com/advisories/GHSA-699m-4v95-rmpm
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-68671
lakeFS is Missing Timestamp Validation in S3 Gateway Authentication
medium6.5Jan 15, 2026CVE-2025-64179
lakeFS affected by unauthenticated access to API usage metrics
medium5.3Nov 3, 2025CVE-2025-27100
lakeFS allows an authenticated user to cause a crash by exhausting server memory
medium6.5Feb 21, 2025CVE-2024-43784
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion
medium5.7Nov 26, 2024GHSA-fvv5-h29g-f6w5
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
medium5.3Feb 22, 2024
