{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66006 exists.","fix":"No fix has been published for CVE-2026-66006 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66006 is a medium-severity missing authorization vulnerability in treeverse lakeFS, published on 24 Jul 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-2026-66006 and fix it if it is affected.\n\nWhat it is: CVE-2026-66006 is a medium-severity missing authorization vulnerability in treeverse lakeFS, published on 24 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66006 exists.\n\nAffected product: treeverse lakeFS. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2026-66006/ (Markdown: https://insights.sbomify.com/CVE-2026-66006/index.md)","id":"CVE-2026-66006","markdown":"https://insights.sbomify.com/CVE-2026-66006/index.md","name":"CVE-2026-66006","record":{"aliases":["GHSA-87fc-9c43-8q4g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"lakeFS data lake","requires_auth":"none","summary":"Unauthenticated attackers can overwrite operator metadata and disable security communications in lakeFS via the setup_comm_prefs endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"lakefs","vendor":"lakefs"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"lakeFS through 1.83.0, fixed in commit 71a45ee, contains an authentication bypass vulnerability in the /setup_comm_prefs endpoint that allows unauthenticated attackers to overwrite operator metadata including email, name, and company after setup completion. Attackers can POST to this endpoint to modify security update preferences, disable security communications, and trigger falsified telemetry events using the legitimate installation ID.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"lakeFS Unauthenticated Operator Metadata Overwrite via setup_comm_prefs","id":"CVE-2026-66006","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Datasets Path Traversal via Unsanitized file_name Metadata","id":"CVE-2026-66007"},"packages":[],"prev":{"headline":"Jan Local API Server CORS Origin Reflection via 0.0.0.0 Binding","id":"CVE-2026-66005"},"products":["lakeFS"],"published":"2026-07-24","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.5,"headline":"lakeFS is Missing Timestamp Validation in S3 Gateway Authentication","id":"CVE-2025-68671","kev_date_added":null,"published":"2026-01-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["treeverse"]},"summary":"Unauthenticated attackers can overwrite operator metadata and disable security communications in lakeFS via the setup_comm_prefs endpoint.","url":"https://insights.sbomify.com/CVE-2026-66006/"}