CVE-2025-68671: lakeFS is Missing Timestamp Validation in S3 Gateway Authentication
Impact 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. Patches This issue affects all versions of lakeFS up to and including v1.74.4.
Published Jan 15, 2026 · Updated Jan 16, 2026
Affected packages
github.com/treeverse/lakefs
- Ecosystem
- Go
- Affected
- < 1.75.0
- Fixed in
- 1.75.0
- Check
go list -m github.com/treeverse/lakefs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Patches
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.
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
References
- https://github.com/treeverse/lakeFS/security/advisories/GHSA-f2ph-gc9m-q55f
- https://github.com/treeverse/lakeFS/issues/9599
- https://github.com/treeverse/lakeFS/pull/9710
- https://github.com/treeverse/lakeFS/commit/92966ae611d7f1a2bbe7fd56f9568c975aab2bd8
- https://nvd.nist.gov/vuln/detail/CVE-2025-68671
- https://github.com/advisories/GHSA-f2ph-gc9m-q55f
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-26187
lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access
high8.1Feb 13, 2026CVE-2025-64179
lakeFS affected by unauthenticated access to API usage metrics
medium5.3Nov 3, 2025CVE-2025-27100
lakeFS allows an authenticated user to cause a crash by exhausting server memory
medium6.5Feb 21, 2025CVE-2024-43784
Re-creating a deleted user in lakeFS will re-enable previous user credentials that existed prior to its deletion
medium5.7Nov 26, 2024GHSA-fvv5-h29g-f6w5
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
medium5.3Feb 22, 2024
