{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-20770 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20770 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20770 is a medium-severity vulnerability in Cluster Management Toolkit for Kubernetes software, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-20770 and fix it if it is affected.\n\nWhat it is: CVE-2026-20770 is a medium-severity vulnerability in Cluster Management Toolkit for Kubernetes software, published on 11 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-20770 in the wild and no public exploit code.\n\nAffected product: Cluster Management Toolkit for Kubernetes software. 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-20770/ (Markdown: https://insights.sbomify.com/CVE-2026-20770/index.md)","id":"CVE-2026-20770","markdown":"https://insights.sbomify.com/CVE-2026-20770/index.md","name":"CVE-2026-20770","record":{"aliases":["GHSA-jgr7-m76x-p9c8"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kubernetes management toolkit","requires_auth":"high_privilege","summary":"A local attacker with privileged access can escalate privileges in the Cluster Management Toolkit for Kubernetes due to a protection mechanism failure.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"intel","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"Protection mechanism failure for some Cluster Management Toolkit for Kubernetes software before version v0.8.5 within Ring 3: User Applications may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires passive user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in Cluster Management Toolkit for Kubernetes software","id":"CVE-2026-20770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in Intel(R) QAT software drivers for Windows","id":"CVE-2026-20771"},"packages":[],"prev":{"headline":"Denial of service in Intel(R) NPU Driver","id":"CVE-2026-20769"},"products":["Cluster Management Toolkit for Kubernetes software"],"published":"2026-08-11","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-08-12","vendors":["n/a"]},"summary":"A local attacker with privileged access can escalate privileges in the Cluster Management Toolkit for Kubernetes due to a protection mechanism failure.","url":"https://insights.sbomify.com/CVE-2026-20770/"}