# CVE-2025-64179: lakeFS: Unauthenticated access to API usage metrics

> Unauthenticated attackers can access aggregate API usage metrics via an unprotected endpoint, revealing service activity information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2025
- **Updated:** 7 Nov 2025
- **Also known as:** GHSA-h238-5mwf-8xw8, GO-2025-4090

## What is CVE-2025-64179?

CVE-2025-64179 is a medium-severity missing authorization vulnerability in treeverse lakeFS, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lakeFS is an open-source tool that transforms object storage into a Git-like repositories. In versions 1.69.0 and below, missing authentication in the /api/v1/usage-report/summary endpoint allows anyone to retrieve aggregate API usage counts. While no sensitive data is disclosed, the endpoint may reveal information about service activity or uptime. This issue is fixed in version 1.71.0 . To workaround the vulnerability, use a load-balancer or application level firewall in order to block the request route /api/v1/usage-report/summary.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-64179?

3 open source packages ship an affected version, including github.com/treeverse/lakefs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/treeverse/lakefs` | Go | All versions | 1.71.0 |
| `github.com/treeverse/lakefs` | Go | All versions | 1.71.0 |
| `github.com/treeverse/lakefs` | Go | All versions | 1.71.0 |

## How do I fix CVE-2025-64179?

Upgrade github.com/treeverse/lakefs to 1.71.0 or later.

## Is CVE-2025-64179 being exploited?

There is no known exploitation of CVE-2025-64179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64179 and fix it if it is affected.

What it is: CVE-2025-64179 is a medium-severity missing authorization vulnerability in treeverse lakeFS, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64179 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.71.0
- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.71.0
- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.71.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64179/ (Markdown: https://insights.sbomify.com/CVE-2025-64179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64179
- OSV: https://osv.dev/vulnerability/CVE-2025-64179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64179/
Summaries are generated and may contain mistakes; the official description above is the record.