CVE-2026-64676

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.7
EG Score
5.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity57% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available. Sources: github.
github Patch Available

kata-agent mem-agent ttRPC methods are not subject to agent-policy enforcement, letting an untrusted host tamper with confidential-guest memory management · Advisory · kata-containers/kata-containers · GitHub

https://github.com/kata-containers/kata-containers/security/advisories/GHSA-h8jv-63p2-496x

Vendor Advisories for CVE-2026-64676(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 01:16 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 00:26 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-17 22:44 UTCEG score recompute
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 21:53 UTCEG score recompute
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-15 21:02 UTCEG score recompute
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 20:10 UTCEG score recompute
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 19:19 UTCEG score recompute
  14. 2026-08-13 18:32 UTCEG score recompute
  15. 2026-08-13 02:46 UTCEG score recompute
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-12 01:56 UTCEG score recompute
  18. 2026-08-11 01:05 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 00:14 UTCEG score recompute
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-08 23:24 UTCEG score recompute
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-07 22:33 UTCEG score recompute
  25. 2026-08-07 21:57 UTCEG score recompute
Show 1 more
  1. 2026-08-07 21:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64676?
CVE-2026-64676 is a medium vulnerability published on August 7, 2026. 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…
When was CVE-2026-64676 disclosed?
CVE-2026-64676 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64676 actively exploited?
CVE-2026-64676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64676?
CVE-2026-64676 has a CVSS v3 base score of 5.7 (NVD).
How do I remediate CVE-2026-64676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64676, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64676

Explore →

Is Your Infrastructure Affected by CVE-2026-64676?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.