CVE-2026-7374

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-26. the CNA's CVSS baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:redhat, epss, ghsa
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to the host's container runtime (CRI-O) socket, an attacker can hijack virt-handler's privileged connection. This enables the attacker to access any Unix socket on the host, potentially leading to full control of the node and the entire cluster.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity99% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

May 26, 2026

Last Modified

August 27, 2026

Advisory Details (12)

Auto-updated Sep 3, 2026
Patch available. Sources: redhat.
redhat

2463728 – (CVE-2026-7374) CVE-2026-7374 kubevirt: KubeVirt virt-handler: Privilege escalation and node compromise via symlink following vulnerability

https://bugzilla.redhat.com/show_bug.cgi?id=2463728
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-7374

Patch Availability(10)

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 rangeFixed inDependents
kubevirt.io/kubevirt1.8.3

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 141× 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.

Showing the most recent 100 of 507 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-7374?
CVE-2026-7374 is a critical vulnerability published on May 26, 2026. A flaw was found in KubeVirt's virt-handler component. This vulnerability allows an authenticated OpenShift user with edit permissions in a single namespace to exploit improper symlink validation when connecting to virtual machine console sockets. By replacing the console socket with a symlink to…
When was CVE-2026-7374 disclosed?
CVE-2026-7374 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7374 actively exploited?
CVE-2026-7374 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.7% of all scored CVEs.
What is the CVSS score of CVE-2026-7374?
CVE-2026-7374 has a CVSS v4.0 base score of 9.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-7374?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7374, 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-7374

Explore →

Is Your Infrastructure Affected by CVE-2026-7374?

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