Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7374 critical CVSS 9.9

Vulnerability in kubevirt.io/kubevirt (CVE-2026-7374)

Summary

Vulnerability in kubevirt.io/kubevirt (CVE-2026-7374). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.6.6 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7374 has been found in kubevirt.io/kubevirt.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade kubevirt.io/kubevirt to 1.6.6 or later.
If unsure, ask your IT team or search "kubevirt.io/kubevirt CVE-2026-7374" on the vendor's site.

CVE-2026-7374 (kubevirt.io/kubevirt) — CWE-59 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.6.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-59) exists in kubevirt.io/kubevirt.

📍 Affected scope

Check the vendor advisory for the affected versions of kubevirt.io/kubevirt.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.6.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'kubevirt.io/kubevirt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'kubevirt.io/kubevirt' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で kubevirt.io/kubevirt を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade kubevirt.io/kubevirt to 1.6.6

    ステージング環境で 1.6.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go kubevirt.io/kubevirt
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.6.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details