How severe is GHSA-m836-gxwq-j2pm?

GHSA-m836-gxwq-j2pm has a CVSS score of 5.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m836-gxwq-j2pm?

GHSA-m836-gxwq-j2pm affects the following packages: github.com/treeverse/lakefs (Go). Ecosystems affected: Go.

How do I fix GHSA-m836-gxwq-j2pm?

Update github.com/treeverse/lakefs to 0.53.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m836-gxwq-j2pm is resolved across your whole dependency graph.

How do I detect GHSA-m836-gxwq-j2pm in my Go dependencies?

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.

How do I mitigate GHSA-m836-gxwq-j2pm if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-m836-gxwq-j2pm?

O3 pinpoints whether GHSA-m836-gxwq-j2pm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m836-gxwq-j2pm actively exploited in the wild?

No public exploit code has been indexed for GHSA-m836-gxwq-j2pm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-m836-gxwq-j2pm published, and has it been updated?

GHSA-m836-gxwq-j2pm was published on October 28, 2021 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-m836-gxwq-j2pm

MEDIUM

Improper Access Control in github.com/treeverse/lakefs

Also known asGO-2022-0375

Published

Oct 28, 2021

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/treeverse/lakefs

Real-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

[medium] A user with write permissions to a portion of a repository may use the S3 gateway to copy any object in the repository if they know its name.
[medium] A user with permission to write any one of tags, branches, or commits on a repository may write all of them.
[low] A user with permission to read any one of tags, branches, or commits on a repository may read all of them.
[low] A user allowed to list objects in a repository or read repository meta-data may retrieve graveler information about the location on underlying storage of all objects stored in any commit that they can view. If the user additionally has the capability to read underlying storage, they will be able to retrieve metadata associated with all objects in that commit.

For more information

If you have any questions or comments about this advisory please:

Email us at [email protected].
Open an issue on https://github.com/treeverse/lakeFS/issues/new.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/treeverse/lakefs`	all versions	0.53.1

Detection & mitigation playbook

Open-source dependency

Detect
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 0.53.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m836-gxwq-j2pm 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-m836-gxwq-j2pm 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-m836-gxwq-j2pm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact 1. [medium] A user with write permissions to a portion of a repository may use the S3 gateway to copy any object in the repository if they know its name. 1. [medium] A user with permission to write any one of tags, branches, or commits on a repository may write all of them. 1. [low] A user with permission to read any one of tags, branches, or commits on a repository may read all of them. 1. [low] A user allowed to list objects in a repository _or_ read repository meta-data may retrieve graveler information about the location on underlying storage of all objects stored in any commit

O3 Security · Impact-Aware SCA

Is GHSA-m836-gxwq-j2pm in your dependencies?

O3 detects GHSA-m836-gxwq-j2pm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works