{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-22806 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22806 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22806 is a critical authentication bypass vulnerability in loft-sh loft, published on 29 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22806 and fix it if it is affected.\n\nWhat it is: CVE-2026-22806 is a critical authentication bypass vulnerability in loft-sh loft, published on 29 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-22806 in the wild and no public exploit code.\n\nAffected product: loft-sh loft. 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-22806/ (Markdown: https://insights.sbomify.com/CVE-2026-22806/index.md)","id":"CVE-2026-22806","markdown":"https://insights.sbomify.com/CVE-2026-22806/index.md","name":"CVE-2026-22806","record":{"aliases":["GHSA-c539-w4ch-7wxq"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes virtual cluster platform","requires_auth":"high_privilege","summary":"Attackers can bypass access key scopes to access resources outside their intended limits, though still restricted by the key owner's permissions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"vCluster Platform provides a Kubernetes platform for managing virtual clusters, multi-tenancy, and cluster sharing. Prior to versions 4.6.0, 4.5.4, 4.4.2, and 4.3.10, when an access key is created with a limited scope, the scope can be bypassed to access resources outside of it. However, the user still cannot access resources beyond what is accessible to the owner of the access key. Versions 4.6.0, 4.5.4, 4.4.2, and 4.3.10 fix the vulnerability. Some other mitigations are available. Users can limit exposure by reviewing access keys which are scoped and ensuring any users with access to them have appropriate permissions set. Creating automation users with very limited permissions and using access keys for these automation users can be used as a temporary workaround where upgrading is not immediately possible but scoped access keys are needed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"vCluster Platform's Access Keys Allows Access Beyond Scope","id":"CVE-2026-22806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"vLLM affected by RCE via auto_map dynamic module loading during model initialization","id":"CVE-2026-22807"},"packages":[],"prev":{"headline":"Metabase channel test endpoint can reach internal local addresses","id":"CVE-2026-22805"},"products":["loft"],"published":"2026-01-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["loft-sh"]},"summary":"Attackers can bypass access key scopes to access resources outside their intended limits, though still restricted by the key owner's permissions.","url":"https://insights.sbomify.com/CVE-2026-22806/"}