Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

KubeVirt has a Link Following vulnerabilityGHSA-7jcp-v9w4-wjmg

CRITICALFix: kubevirt/kubevirt#17916

GHSA-7jcp-v9w4-wjmg is a critical-severity (CVSS 9.9) CWE-59 vulnerability in kubevirt.io/kubevirt. A fix is available for kubevirt.io/kubevirt — see the affected versions and patch details below.

Also known asCVE-2026-7374GO-2026-5848
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7jcp-v9w4-wjmg.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.44%0.89%1.33%0.1%0.6%0.7%0.8%0.8%Jun 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-7jcp-v9w4-wjmg by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,189 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
🐹kubevirt.io/kubevirt🐹kubevirt.io/kubevirt🐹kubevirt.io/kubevirt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gokubevirt.io/kubevirt≥ 1.8.0-alpha.0&&< 1.8.31.8.3go get kubevirt.io/kubevirt@v1.8.3
🐹Gokubevirt.io/kubevirt≥ 1.7.0-alpha.0&&< 1.7.41.7.4go get kubevirt.io/kubevirt@v1.7.4
🐹Gokubevirt.io/kubevirtall versions1.6.6go get kubevirt.io/kubevirt@v1.6.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kubevirt.io/kubevirt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update kubevirt.io/kubevirt to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jcp-v9w4-wjmg is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important privilege escalation flaw in KubeVirt's virt-handler component. An authenticated OpenShift user with edit permissions in a single namespace can exploit improper symlink validation to hijack virt-handler's privileged connection. This allows access to any Unix socket on the host, leading to…

Workaround published by Red Hat
Update cluster RBAC to not allow exec into virt-launcher pods.
Source: Red Hat security advisory for GHSA-7jcp-v9w4-wjmg (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Container Native Virtualization 4.12container-native-virtualization/virt-handler:1779375376RHSA-2026:20825
Red Hat Container Native Virtualization 4.13container-native-virtualization/virt-handler-rhel9:1778999881RHSA-2026:20886
Red Hat Container Native Virtualization 4.14container-native-virtualization/virt-handler-rhel9:1779321599RHSA-2026:20890
Red Hat Container Native Virtualization 4.15container-native-virtualization/virt-handler-rhel9:1778859977RHSA-2026:20866
Red Hat Container Native Virtualization 4.16container-native-virtualization/virt-handler-rhel9:1778861274RHSA-2026:20975
Red Hat Container Native Virtualization 4.17container-native-virtualization/virt-handler-rhel9:1779174925RHSA-2026:20763
Red Hat Container Native Virtualization 4.18container-native-virtualization/virt-handler-rhel9:1778887155RHSA-2026:20736
Red Hat Container Native Virtualization 4.19container-native-virtualization/virt-handler-rhel9:1779289071RHSA-2026:20767

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-7jcp-v9w4-wjmg in your dependencies?

Find it across Go, including transitive dependencies.

KubeVirt has a Link Following vulnerability (Critical 9.9)