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.2% (6th percentile of EPSS-scored CVEs). 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.2%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

September 9, 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 10× in last 7d / 41× 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-10-05 08:11 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 05:41 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 09:29 UTCEG score recompute
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 22:54 UTCEG score recompute
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 05:42 UTCEG score recompute
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 17:06 UTCEG score recompute
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-25 04:12 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescore
  16. 2026-09-23 13:46 UTCEG score recompute
  17. 2026-09-22 12:52 UTCEG score recompute
  18. 2026-09-21 12:01 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 10:54 UTCEG score recompute
  21. 2026-09-19 07:54 UTCEG score recompute
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-18 07:03 UTCEG score recompute
  24. 2026-09-17 06:12 UTCEG score recompute
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 64 more
  1. 2026-09-16 05:20 UTCEG score recompute
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 04:29 UTCEG score recompute
  4. 2026-09-14 03:36 UTCEG score recompute
  5. 2026-09-13 02:45 UTCEG score recompute
  6. 2026-09-12 01:54 UTCEG score recompute
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-11 01:03 UTCEG score recompute
  10. 2026-09-09 05:59 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 17:42 UTCEG score recompute
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 10:33 UTCEG score recompute
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-05 09:41 UTCEG score recompute
  18. 2026-09-04 08:50 UTCEG score recompute
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-03 04:02 UTCEG score recompute
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 23:18 UTCEG score recompute
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-31 22:26 UTCEG score recompute
  26. 2026-08-30 19:17 UTCEPSS rescore
  27. 2026-08-30 16:48 UTCEG score recompute
  28. 2026-08-30 01:22 UTCEPSS rescore
  29. 2026-08-29 15:57 UTCEG score recompute
  30. 2026-08-28 21:42 UTCEPSS rescore
  31. 2026-08-28 11:52 UTCEG score recompute
  32. 2026-08-27 07:50 UTCEG score recompute
  33. 2026-08-26 14:47 UTCEPSS rescore
  34. 2026-08-26 05:45 UTCEG score recompute
  35. 2026-08-25 13:49 UTCEPSS rescore
  36. 2026-08-25 04:54 UTCEG score recompute
  37. 2026-08-22 02:21 UTCEG score recompute
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-21 01:16 UTCEG score recompute
  40. 2026-08-20 22:55 UTCEPSS rescore
  41. 2026-08-20 00:26 UTCEG score recompute
  42. 2026-08-19 17:04 UTCEPSS rescore
  43. 2026-08-17 22:44 UTCEG score recompute
  44. 2026-08-17 13:47 UTCEPSS rescore
  45. 2026-08-16 21:53 UTCEG score recompute
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-15 21:02 UTCEG score recompute
  48. 2026-08-15 01:30 UTCEPSS rescore
  49. 2026-08-14 20:10 UTCEG score recompute
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 19:19 UTCEG score recompute
  52. 2026-08-13 18:32 UTCEG score recompute
  53. 2026-08-13 02:46 UTCEG score recompute
  54. 2026-08-12 13:51 UTCEPSS rescore
  55. 2026-08-12 01:56 UTCEG score recompute
  56. 2026-08-11 01:05 UTCEG score recompute
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-10 00:14 UTCEG score recompute
  59. 2026-08-09 13:47 UTCEPSS rescore
  60. 2026-08-08 23:24 UTCEG score recompute
  61. 2026-08-08 16:37 UTCEPSS rescore
  62. 2026-08-07 22:33 UTCEG score recompute
  63. 2026-08-07 21:57 UTCEG score recompute
  64. 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 on August 7, 2026, with the most recent update on September 9, 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.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64676?
CVE-2026-64676 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64676?
A fix for CVE-2026-64676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64676 are linked in the Vendor Advisories panel on this page.

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.