CVE-2026-64676

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-54711 (ENISA EUVD)Source: ENISA EUVD

5.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.7Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — 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/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 7, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

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 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 123 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-30 08:25 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-25 14:12 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-22 19:42 UTCEG score recompute
  12. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-18 03:22 UTCEG score recompute
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-12 15:47 UTCEG score recompute
  24. 2026-10-11 19:32 UTCEG score recompute
  25. 2026-10-11 16:47 UTCEG score recompute
Show 75 more
  1. 2026-10-11 14:08 UTCEG score recompute
  2. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-06 23:16 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-05 08:11 UTCEG score recompute
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-04 05:41 UTCEG score recompute
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-02 09:29 UTCEG score recompute
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-30 22:54 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-29 05:42 UTCEG score recompute
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-27 17:06 UTCEG score recompute
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-25 04:12 UTCEG score recompute
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-23 13:46 UTCEG score recompute
  26. 2026-09-22 12:52 UTCEG score recompute
  27. 2026-09-21 12:01 UTCEG score recompute
  28. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-20 10:54 UTCEG score recompute
  30. 2026-09-19 07:54 UTCEG score recompute
  31. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-18 07:03 UTCEG score recompute
  33. 2026-09-17 06:12 UTCEG score recompute
  34. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-16 05:20 UTCEG score recompute
  36. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-09-15 04:29 UTCEG score recompute
  38. 2026-09-14 03:36 UTCEG score recompute
  39. 2026-09-13 02:45 UTCEG score recompute
  40. 2026-09-12 01:54 UTCEG score recompute
  41. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-09-11 01:03 UTCEG score recompute
  44. 2026-09-09 05:59 UTCEG score recompute
  45. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-09-07 17:42 UTCEG score recompute
  47. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-09-06 10:33 UTCEG score recompute
  50. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-09-05 09:41 UTCEG score recompute
  52. 2026-09-04 08:50 UTCEG score recompute
  53. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-09-03 04:02 UTCEG score recompute
  55. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-09-01 23:18 UTCEG score recompute
  57. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  59. 2026-08-31 22:26 UTCEG score recompute
  60. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  61. 2026-08-30 16:48 UTCEG score recompute
  62. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  63. 2026-08-29 15:57 UTCEG score recompute
  64. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-08-28 11:52 UTCEG score recompute
  66. 2026-08-27 07:50 UTCEG score recompute
  67. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  68. 2026-08-26 05:45 UTCEG score recompute
  69. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  70. 2026-08-25 04:54 UTCEG score recompute
  71. 2026-08-22 02:21 UTCEG score recompute
  72. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  73. 2026-08-21 01:16 UTCEG score recompute
  74. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  75. 2026-08-20 00:26 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64676?
CVE-2026-64676 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-64676 published?
The CVE record for CVE-2026-64676 was published on August 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
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 (7th 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?
The CVE record for CVE-2026-64676 names the fix: "This issue is fixed in version 4.0.0." 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.

Book a Demo →Browse All CVEs