{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64676 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64676 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64676 is a medium-severity missing authorization vulnerability in kata-containers, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64676 and fix it if it is affected.\n\nWhat it is: CVE-2026-64676 is a medium-severity missing authorization vulnerability in kata-containers, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64676 in the wild and no public exploit code.\n\nAffected product: kata-containers. 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-64676/ (Markdown: https://insights.sbomify.com/CVE-2026-64676/index.md)","id":"CVE-2026-64676","markdown":"https://insights.sbomify.com/CVE-2026-64676/index.md","name":"CVE-2026-64676","record":{"aliases":["AZL-94685","GHSA-h8jv-63p2-496x"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Kata Containers","requires_auth":"none","summary":"An untrusted host can tamper with confidential guest memory management, causing performance degradation and availability issues, if the mem-agent feature is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Kata Containers is an open source implementation of lightweight Virtual Machines (VMs) that perform like containers. In versions prior to 4.0.0, the kata-agent is vulnerable to an authorization bypass in confidential-guest memory management. In Confidential Containers (CoCo) deployments, the kata-agent enforces an OPA/Rego-based AgentPolicy that must authorize every ttRPC API call, forming the security boundary that prevents an untrusted host from directing the confidential guest. Two ttRPC methods introduced with the mem-agent feature are missing this authorization check, so an untrusted host can invoke them unconditionally regardless of the guest's policy configuration. When mem-agent is enabled (off by default), this lets the host tamper with in-guest memory management by forcing swap, aggressive eviction, or compaction, resulting in attacker-controlled availability and performance degradation of the confidential workload entirely outside the agent-policy boundary. The impact does not include memory disclosure or code execution, and severity is bounded by the precondition that mem-agent must be explicitly enabled. This issue is fixed in version 4.0.0.","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":"Kata Containers: Unauthorized mem-agent ttRPC methods let an untrusted host tamper with confidential-guest memory","id":"CVE-2026-64676","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Anki's local HTTP server is vulnerable to directory traversal attacks","id":"CVE-2026-64677"},"packages":[],"prev":{"headline":"Statamic: Account takeover via OAuth email matching without email-verification check","id":"CVE-2026-64665"},"products":["kata-containers"],"published":"2026-08-07","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":"partial"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["kata-containers"]},"summary":"An untrusted host can tamper with confidential guest memory management, causing performance degradation and availability issues, if the mem-agent feature is enabled.","url":"https://insights.sbomify.com/CVE-2026-64676/"}