CVE-2026-7374

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-26. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-31824 (ENISA EUVD) · GHSA-7jcp-v9w4-wjmg (GitHub Security Advisories) · GO-2026-5848 (OSV.dev)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

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.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
0.7%
EPSS %ILE
55th
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.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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 or medium mission impact; Track* at high (mission-essential systems).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, 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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.

The score's inputs: 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 26, 2026

Last Modified

September 10, 2026

Advisory Details (12)

Auto-updated Nov 6, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20975
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20890
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20866
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20825
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20782
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20767
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20763
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20736
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20720
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:20886
Red Hat

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
Red HatMentions a patch (unverified)

cve-details

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcontainer-native-virtualization/virt-handler-rhel9:17788599772026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17788612742026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17792890712026-05-26redhat
redhatcontainer-native-virtualization/virt-handler:17793753762026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17788871552026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17789998812026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17793215992026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17791749252026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17792887372026-05-26redhat
redhatcontainer-native-virtualization/virt-handler-rhel9:17794200692026-05-26redhat
gokubevirt.io/kubevirt @ 1.8.3 (fixes >= 1.8.0-alpha.0, < 1.8.3)—ghsa
gokubevirt.io/kubevirt @ 1.7.4 (fixes >= 1.7.0-alpha.0, < 1.7.4)—ghsa
gokubevirt.io/kubevirt @ 1.6.6 (fixes < 1.6.6)—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
kubevirt.io/kubevirt—
  • 1.8.0-alpha.0 up to 1.8.3: fixed in 1.8.3
  • 1.7.0-alpha.0 up to 1.7.4: fixed in 1.7.4
  • every version up to 1.6.6: fixed in 1.6.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 72× 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 663 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 563 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-7374?
CVE-2026-7374 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-7374 was made public on May 26, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-7374 actively exploited?
CVE-2026-7374 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-7374?
CVE-2026-7374 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-7374?
A fix for CVE-2026-7374 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-7374 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-7374

Explore →

Is Your Infrastructure Affected by CVE-2026-7374?

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