CVE-2026-44210

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-48339 (ENISA EUVD) · GHSA-rr59-xxvx-96qr (GitHub Security Advisories) · GO-2026-5638 (OSV.dev)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Versions prior to 3.31.0 ship with a default configuration that allows pod creators to inject arbitrary command-line arguments into the virtiofsd process through the io.katacontainers.config.hypervisor.virtio_fs_extra_args pod annotation. By injecting -o source=/ along with --no-announce-submounts and --sandbox=none, an attacker can override the virtiofsd shared directory to serve the entire host root filesystem into the guest VM. Combined with the kernel_params annotation (also enabled by default) to activate the agent debug console, the attacker can mount the host filesystem from inside the VM and read or write any file on the host, including /etc/shadow. Version 3.31.0 patches the issue.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

May 26, 2026

Last Modified

August 6, 2026

Advisory Details (2)

Auto-updated Nov 6, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

VM Escape via virtiofsd Argument Injection through Default-Enabled Pod Annotations · Advisory · kata-containers/kata-containers · GitHub

https://github.com/kata-containers/kata-containers/security/advisories/GHSA-rr59-xxvx-96qr
GitHub commit

commit ffa59ce3aa78 (kata-containers/kata-containers)

Fix landed in kata-containers/kata-containers commit ffa59ce3aa78 — awaiting tagged release

https://github.com/kata-containers/kata-containers/commit/ffa59ce3aa7877d067c9a372df0c329a23a01744

Vendor Advisories for CVE-2026-44210(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/kata-containers/kata-containers @ 0.0.0-20260519062212-ffa59ce3aa78 (fixes < 0.0.0-20260519062212-ffa59ce3aa78)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/kata-containers/kata-containers—
  • every version up to 0.0.0-20260519062212-ffa59ce3aa78: fixed in 0.0.0-20260519062212-ffa59ce3aa78
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 65× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 243 rows 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 143 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-44210?
CVE-2026-44210 is a critical-severity vulnerability; its CVE record was published on May 26, 2026. Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Versions prior to 3.31.0 ship with a default configuration that allows pod creators to inject arbitrary command-line arguments into the virtiofsd…
When was the CVE record for CVE-2026-44210 published?
The CVE record for CVE-2026-44210 was published on May 26, 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 August 6, 2026; the record at its source may have been updated since.
Is CVE-2026-44210 actively exploited?
CVE-2026-44210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44210?
CVE-2026-44210 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-44210?
A fix for CVE-2026-44210 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44210 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44210

Explore →

Is Your Infrastructure Affected by CVE-2026-44210?

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