CVE-2026-47243

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th 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
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-54710 (ENISA EUVD) · GHSA-2gv2-cffp-j227 (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
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.2%CVSS: 9.2Exploit: 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. Prior to 3.31.0, the runtime-rs standalone virtio-fs path is vulnerable to a guest-root to host-root escape. In this configuration, Kata runs the host virtiofsd as root with --sandbox none --seccomp none, so an attacker with root-equivalent access inside the guest can bypass the guest virtio-fs client entirely by taking over the virtio-fs PCI device and building a virtqueue in userspace to submit raw FUSE requests directly to the host virtiofsd. A crafted FUSE_SYMLINK request whose new symlink name is an absolute host path is honored outside the configured shared directory, allowing guest root to create root-owned symlinks in sensitive host locations such as /etc/cron.d. By pointing such a symlink at a guest-controlled crontab payload reachable through a live runtime process's mount namespace, the attacker causes the host cron daemon to execute that payload as host root, crossing the Kata isolation boundary. This issue is fixed in version 3.31.0.

CVSS v3
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (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 no (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.2%
EPSS %ILE
9th
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.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-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-30). 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: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: 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 no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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 27, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

runtime-rs: Guest-root to host-root escape via virtiofs · Advisory · kata-containers/kata-containers · GitHub

https://github.com/kata-containers/kata-containers/security/advisories/GHSA-2gv2-cffp-j227
Web page

oss-security - CVE-2026-47243: Kata Containers runtime-rs 3.30: virtiofsd symlink escape

http://www.openwall.com/lists/oss-security/2026/05/21/14

Vendor Advisories for CVE-2026-47243(2)

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

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(2)

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

Data Freshness Timeline

(refreshed 18× 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 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 139 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 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/kata-containers/kata-containers

Frequently asked(5)

What is CVE-2026-47243?
CVE-2026-47243 is a critical-severity vulnerability; its CVE record was published on May 27, 2026. Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Prior to 3.31.0, the runtime-rs standalone virtio-fs path is vulnerable to a guest-root to host-root escape. In this configuration, Kata runs the host…
When was the CVE record for CVE-2026-47243 published?
The CVE record for CVE-2026-47243 was published on May 27, 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-47243 actively exploited?
CVE-2026-47243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47243?
CVE-2026-47243 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47243?
A fix for CVE-2026-47243 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47243 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-47243

Explore →

Is Your Infrastructure Affected by CVE-2026-47243?

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

Book a Demo →Browse All CVEs