Is github.com/treeverse/lakefs 0.109 vulnerable?
Go · 1 release from 0.109.0 to 0.109.0 · latest github.com/treeverse/lakefs is 1.88.0 · checked 18 Nov 2026
Yes: 14 known advisories
Yes. github.com/treeverse/lakefs 0.109.0, the last 0.109 release, is affected by 14 known security advisories (1 high, 6 medium, 7 low), including CVE-2026-26187, CVE-2025-68671, CVE-2025-64179. Upgrade to 1.77.0 or later to fix all of them.
go get github.com/treeverse/lakefs@v1.77.0Is your project on an affected github.com/treeverse/lakefs?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/treeverse/lakefs 0.109.0
lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access in github.com/treeverse/lakefs
- Affected
- <1.77.0
- Fixed in
- 1.77.0
lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access
- Affected
- <1.77.0
- Fixed in
- 1.77.0
lakeFS is Missing Timestamp Validation in S3 Gateway Authentication in github.com/treeverse/lakefs
- Affected
- <1.75.0
- Fixed in
- 1.75.0
lakeFS is Missing Timestamp Validation in S3 Gateway Authentication
- Affected
- <1.75.0
- Fixed in
- 1.75.0
lakeFS affected by unauthenticated access to API usage metrics in github.com/treeverse/lakefs
- Affected
- <1.71.0
- Fixed in
- 1.71.0
lakeFS affected by unauthenticated access to API usage metrics
- Affected
- <1.71.0
- Fixed in
- 1.71.0
lakeFS allows an authenticated user to cause a crash by exhausting server memory in github.com/treeverse/lakefs
- Affected
- <1.50.0
- Fixed in
- 1.50.0
lakeFS allows an authenticated user to cause a crash by exhausting server memory
- Affected
- <1.50.0
- Fixed in
- 1.50.0
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion in github.com/treeverse/lakefs
- Affected
- <1.33.0
- Fixed in
- 1.33.0
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion
- Affected
- <1.33.0
- Fixed in
- 1.33.0
User with permission to write actions can impersonate another user when auth token is configured in environment variable in github.com/treeverse/lakefs
- Affected
- <1.3.1
- Fixed in
- 1.3.1
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository in github.com/treeverse/lakefs
- Affected
- >=0.90.0 <1.12.1
- Fixed in
- 1.12.1
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
- Affected
- >=0.90.0 <1.12.1
- Fixed in
- 1.12.1
User with permission to write actions can impersonate another user when auth token is configured in environment variable
- Affected
- <1.3.1
- Fixed in
- 1.3.1
Which of your client projects are still on github.com/treeverse/lakefs 0.109?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/treeverse/lakefs version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/treeverse/lakefs versions
- github.com/treeverse/lakefs 0.112
- github.com/treeverse/lakefs 0.111
- github.com/treeverse/lakefs 0.110
- github.com/treeverse/lakefs 0.108
- github.com/treeverse/lakefs 0.107
- github.com/treeverse/lakefs 0.106
- github.com/treeverse/lakefs 1.88
- github.com/treeverse/lakefs 1.87
- github.com/treeverse/lakefs 1.86
- github.com/treeverse/lakefs 1.85
- github.com/treeverse/lakefs 1.84
- github.com/treeverse/lakefs 1.83
- All github.com/treeverse/lakefs advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.