CVE-2026-47243

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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
Trending — 3 sources updated this weekElevated
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.2Exploit: Elevated riskExposed: 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 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.2(medium)
EG Risk
57(Track*)
EG Risk 57/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
Severity92% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 27, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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
generic

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 rangeFixed inDependents
github.com/kata-containers/kata-containers0.0.0-20260519062212-ffa59ce3aa78

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 07:32 UTCEG score recompute
  3. 2026-09-14 07:32 UTCVendor advisory
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 09:37 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-09 23:00 UTCEG score recompute
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 05:08 UTCEG score recompute
  23. 2026-08-25 05:08 UTCVendor advisory
  24. 2026-08-23 23:56 UTCVendor advisory
  25. 2026-08-23 18:46 UTCVendor advisory
Show 40 more
  1. 2026-08-23 14:51 UTCEG score recompute
  2. 2026-08-23 14:51 UTCVendor advisory
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 00:38 UTCEG score recompute
  5. 2026-08-22 00:38 UTCVendor advisory
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 01:28 UTCEG score recompute
  8. 2026-08-21 01:28 UTCVendor advisory
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 11:11 UTCEG score recompute
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 15:12 UTCEG score recompute
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:42 UTCEG score recompute
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 01:22 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 13:52 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 18:29 UTCEG score recompute
  24. 2026-08-11 00:09 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 14:31 UTCEG score recompute
  27. 2026-08-09 14:24 UTCEG score recompute
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-08 18:49 UTCEG score recompute
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 23:34 UTCEG score recompute
  32. 2026-08-07 21:57 UTCEG score recompute 9.20
  33. 2026-08-07 21:57 UTCMITRE cvelistV5CVSS v3 → 9.2 · CVSS v4 → 9.2 · severity → CRITICAL
  34. 2026-07-31 07:04 UTCEG score recompute
  35. 2026-07-27 09:56 UTCEG score recompute
  36. 2026-07-23 03:17 UTCEG score recompute
  37. 2026-06-14 23:18 UTCEPSS rescore
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-12 23:12 UTCEPSS rescore
  40. 2026-05-27 23:04 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47243?
CVE-2026-47243 is a critical vulnerability 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 CVE-2026-47243 disclosed?
CVE-2026-47243 was first published in the National Vulnerability Database on May 27, 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-47243 actively exploited?
CVE-2026-47243 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 71.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47243?
CVE-2026-47243 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-47243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47243, 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

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.