CVE-2025-68671

Workarounds

Until upgraded, implement these mitigations:

• Use short-lived credentials - Rotate access keys frequently and deactivate old keys. For regular requests, captured requests only work until rotation. For presigned URLs, they remain valid until the credentials used to create them are deactivated.
• Network controls - Restrict S3 gateway access to trusted networks/IPs to limit where replay attacks can originate.

Note: These workarounds reduce risk but do not fully eliminate the vulnerability.

References

• Original issue: https://github.com/treeverse/lakeFS/issues/9599
• AWS Signature V4 Documentation: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html
• AWS Signature V4 S3 Requests: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
• AWS Signature V2 Documentation: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html

LakeFS's S3 gateway does not validate timestamps in authenticated requests, allowing replay attacks. An attacker who captures a valid signed request (e.g., through network interception, logs, or compromised systems) can replay that request until credentials are rotated, even after the request is intended to expire.

CVE-2025-68671 has a CVSS score of 6.5 (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.75.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue affects all versions of lakeFS up to and including v1.74.4.

The vulnerability has been fixed in version v1.75.0.

Users should upgrade to version v1.75.0.

1. What is CVE-2025-68671? CVE-2025-68671 is a medium-severity security vulnerability in github.com/treeverse/lakefs (go), affecting versions < 1.75.0. It is fixed in 1.75.0.
2. How severe is CVE-2025-68671? CVE-2025-68671 has a CVSS score of 6.5 (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.
3. Which versions of github.com/treeverse/lakefs are affected by CVE-2025-68671? github.com/treeverse/lakefs (go) versions < 1.75.0 is affected.
4. Is there a fix for CVE-2025-68671? Yes. CVE-2025-68671 is fixed in 1.75.0. Upgrade to this version or later.
5. Is CVE-2025-68671 exploitable, and should I be worried? Whether CVE-2025-68671 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
6. What actually determines whether CVE-2025-68671 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.
7. How do I fix CVE-2025-68671? Upgrade github.com/treeverse/lakefs to 1.75.0 or later.