What is CVE-2025-64179?

CVE-2025-64179 is a medium-severity missing authorization vulnerability in github.com/treeverse/lakefs (go), affecting versions < 1.71.0. It is fixed in 1.71.0. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2025-64179?

CVE-2025-64179 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/treeverse/lakefs are affected by CVE-2025-64179?

github.com/treeverse/lakefs (go) versions < 1.71.0 is affected.

Is there a fix for CVE-2025-64179?

Yes. CVE-2025-64179 is fixed in 1.71.0. Upgrade to this version or later.

Is CVE-2025-64179 exploitable, and should I be worried?

Whether CVE-2025-64179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-64179 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-64179?

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

CVE-2025-64179 in github.com/treeverse/lakefs | Intelligent Application Security

Q: How severe is CVE-2025-64179?

CVE-2025-64179 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/treeverse/lakefs are affected by CVE-2025-64179?

github.com/treeverse/lakefs (go) versions < 1.71.0 is affected.

Q: Is there a fix for CVE-2025-64179?

Yes. CVE-2025-64179 is fixed in 1.71.0. Upgrade to this version or later.

Q: Is CVE-2025-64179 exploitable, and should I be worried?

Whether CVE-2025-64179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-64179 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-64179?

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

Summary

Workarounds

Any ONE of these is sufficient to block this reporting:

Disable usage reporting by setting configuration option usage_report.enabled or environment variable LAKEFS_USAGE_REPORT_ENABLED to false.
Using load-balancer or application level firewall - blocking the request route /api/v1/usage-report/summary.

Impact

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2025-64179 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.71.0); upgrading removes the vulnerable code path.

Affected versions

github.com/treeverse/lakefs (< 1.71.0)

Security releases

github.com/treeverse/lakefs → 1.71.0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade to >v1.70.1

Frequently Asked Questions

What is CVE-2025-64179? CVE-2025-64179 is a medium-severity missing authorization vulnerability in github.com/treeverse/lakefs (go), affecting versions < 1.71.0. It is fixed in 1.71.0. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2025-64179? CVE-2025-64179 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/treeverse/lakefs are affected by CVE-2025-64179? github.com/treeverse/lakefs (go) versions < 1.71.0 is affected.
Is there a fix for CVE-2025-64179? Yes. CVE-2025-64179 is fixed in 1.71.0. Upgrade to this version or later.
Is CVE-2025-64179 exploitable, and should I be worried? Whether CVE-2025-64179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-64179 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-64179? Upgrade github.com/treeverse/lakefs to 1.71.0 or later.

Other vulnerabilities in github.com/treeverse/lakefs

CVE-2026-26187 CVE-2025-64179 CVE-2025-27100 CVE-2024-43784