https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 00:46:36 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-266066 EUVD-2026-266066 https://cve.radiocsirt.org/vuln/euvd-2026-266066 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68671 <p>lakeFS is an open-source tool that transforms object storage into a Git-like repositories. LakeFS&#39;s S3 gateway does not validate timestamps in authenticated requests, allowing replay attacks. Prior to 1.75.0, 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. This vulnerability is fixed in 1.75.0.</p> <p>lakeFS is an open-source tool that transforms object storage into a Git-like repositories. LakeFS&#39;s S3 gateway does not validate timestamps in authenticated requests, allowing replay attacks. Prior to 1.75.0, 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. This vulnerability is fixed in 1.75.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68671 https://cve.radiocsirt.org/vuln/ghsa-f2ph-gc9m-q55f <p><strong>Affected:</strong> Go: github.com/treeverse/lakefs</p> <p>### Impact LakeFS&#39;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.</p> <p>### Patches This issue affects all versions of lakeFS up to and including v1.74.4.</p> <p>The vulnerability has been fixed in version v1.75.0.</p> <p>Users should upgrade to version v1.75.0.</p> <p>### Workarounds</p> <p>Until upgraded, implement these mitigations:</p> <p>- **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.</p> <p>Note: These workarounds reduce risk but do not fully eliminate the vulnerability.</p> <p>### 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</p> <p><strong>Affected:</strong> Go: github.com/treeverse/lakefs</p> <p>### Impact LakeFS&#39;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.</p> <p>### Patches This issue affects all versions of lakeFS up to and including v1.74.4.</p> <p>The vulnerability has been fixed in version v1.75.0.</p> <p>Users should upgrade to version v1.75.0.</p> <p>### Workarounds</p> <p>Until upgraded, implement these mitigations:</p> <p>- **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.</p> <p>Note: These workarounds reduce risk but do not fully eliminate the vulnerability.</p> <p>### 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</p> https://cve.radiocsirt.org/vuln/ghsa-f2ph-gc9m-q55f