Skip to main content
VulnerabilityPublished Updated

CVE-2026-13622: Red Hat Container Native Virtualization 4.12 · Path Traversal

Affects Red Hat Container Native Virtualization 4.12Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red HatRed Hat Container Native Virtualization 4.12Affected–Fixed in–
Red HatRed Hat Container Native Virtualization 4.13Affected–Fixed in–
Red HatRed Hat Container Native Virtualization 4.14Affected–Fixed in–
Red HatRed Hat Container Native Virtualization 4.15Affected–Fixed in–
Red HatRed Hat Container Native Virtualization 4.16Affected–Fixed in–
Red HatRed Hat Container Native Virtualization 4.17Affected–Fixed in–

AI-suggested

Red Hat advises restricting pods/exec permissions in namespaces running virtual machines, as pods/exec RBAC permission is required for exploitation. Removing pods/exec permission from VM operator roles prevents exploitation. Additionally, enable Kubernetes audit logging and monitor for kubectl exec commands targeting virt-launcher pods, especially during live migration events.

Description

A symlink following vulnerability was found in KubeVirt's virt-handler migration proxy. During live migration, virt-handler dials Unix sockets inside the target virt-launcher pod via /proc/<pid>/root/ paths using net.Dial() without symlink protection. These socket paths reside in qemu-owned directories writable by the virt-launcher user. An attacker with namespace edit and pods/exec permissions can replace a migration proxy socket with a symlink to the host CRI-O socket. Because virt-handler runs as root in the host mount namespace, absolute symlink targets resolve against the host filesystem, and the bidirectional io.Copy proxy relays attacker-controlled bytes to the container runtime, enabling full node compromise.

References

Community reviews

Loading reviews…