{"answers":{"affected":"3 open source packages ship an affected version, including github.com/treeverse/lakefs. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-68671 in the wild and no public exploit code.","fix":"Upgrade github.com/treeverse/lakefs to 1.75.0 or later.","what":"CVE-2025-68671 is a medium-severity vulnerability in treeverse lakeFS, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68671 and fix it if it is affected.\n\nWhat it is: CVE-2025-68671 is a medium-severity vulnerability in treeverse lakeFS, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-68671 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.75.0\n- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.75.0\n- github.com/treeverse/lakefs (Go): affected all versions; fixed in 1.75.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68671/ (Markdown: https://insights.sbomify.com/CVE-2025-68671/index.md)","id":"CVE-2025-68671","markdown":"https://insights.sbomify.com/CVE-2025-68671/index.md","name":"CVE-2025-68671","record":{"aliases":["GHSA-f2ph-gc9m-q55f","GO-2026-4321"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Object storage gateway","requires_auth":"none","summary":"Attackers can replay captured signed requests indefinitely due to missing timestamp validation in the S3 gateway, bypassing expiration controls.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"lakefs","vendor":"lakefs"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"lakeFS is an open-source tool that transforms object storage into a Git-like repositories. LakeFS'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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"lakeFS is Missing Timestamp Validation in S3 Gateway Authentication","id":"CVE-2025-68671","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"Apache Airflow: proxy credentials for various providers might leak in task logs","id":"CVE-2025-68675"},"packages":[{"ecosystem":"Go","fixed":["1.75.0"],"introduced":["0"],"last_affected":[],"package":"github.com/treeverse/lakefs","purl":null,"source":"GHSA-f2ph-gc9m-q55f"},{"ecosystem":"Go","fixed":["1.75.0"],"introduced":["0"],"last_affected":[],"package":"github.com/treeverse/lakefs","purl":"pkg:golang/github.com/treeverse/lakefs","source":"GHSA-f2ph-gc9m-q55f"},{"ecosystem":"Go","fixed":["1.75.0"],"introduced":["0"],"last_affected":[],"package":"github.com/treeverse/lakefs","purl":"pkg:golang/github.com/treeverse/lakefs","source":"GO-2026-4321"}],"prev":{"headline":"xrdp improperly checks bounds of domain string length, which leads to Stack-based Buffer Overflow","id":"CVE-2025-68670"},"products":["lakeFS"],"published":"2026-01-15","related":[{"cvss_score":8.1,"headline":"lakeFS vulnerable to path traversal in local block adapter allow cross-namespace and sibling directory access","id":"CVE-2026-26187","kev_date_added":null,"published":"2026-02-13"},{"cvss_score":6.9,"headline":"lakeFS Unauthenticated Operator Metadata Overwrite via setup_comm_prefs","id":"CVE-2026-66006","kev_date_added":null,"published":"2026-07-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-20","vendors":["treeverse"]},"summary":"Attackers can replay captured signed requests indefinitely due to missing timestamp validation in the S3 gateway, bypassing expiration controls.","url":"https://insights.sbomify.com/CVE-2025-68671/"}