GHSA-j7jw-28jm-whr6 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in github.com/treeverse/lakefs. O3 Security confirms whether GHSA-j7jw-28jm-whr6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
lakeFS allows an authenticated user to cause a crash by exhausting server memory
Real-World Exposure
github.com/treeverse/lakefsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
An authenticated user can crash lakeFS by exhausting server memory. This is an authenticated denial-of-service issue.
Patches
This problem has been patched and exists in versions 1.49.1 and below
Workarounds
On S3 backends, configure
# ...
blockstore:
s3:
disable_pre_signed_multipart: true
or set environment variable LAKEFS_BLOCKSTORE_S3_DISABLE_PRE_SIGNED_MULTIPART to true.
References
Are there any links users can visit to find out more?
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/treeverse/lakefs | all versions | 1.50.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/treeverse/lakefs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/treeverse/lakefs to 1.50.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7jw-28jm-whr6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j7jw-28jm-whr6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-j7jw-28jm-whr6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j7jw-28jm-whr6 in your dependencies?
O3 detects GHSA-j7jw-28jm-whr6 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.