CyberSecBulletin
CVE-2026-13201NVD status: Modified

Red Hat Container Native Virtualization 4.12: UNIX Symbolic Link (Symlink) Following

Published Updated By the CyberSecBulletin desk

CVE-2026-13201 is a high-severity UNIX symbolic link (symlink) following vulnerability in Red Hat Container Native Virtualization 4.12 from Red Hat, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Red Hat Container Native Virtualization 4.12 you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on access.redhat.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat Container Native Virtualization 4.12Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.13Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.14Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.15Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.16Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.17Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.18Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.19Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.20Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.21Not specified in the recordNot stated
Red HatRed Hat Container Native Virtualization 4.22Not specified in the recordNot stated
KubevirtKubevirtNot specified in the recordNot stated
Red HatOpenshift Virtualization4 through 4.22.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
NoneNo data is disclosed.
Integrity
LowLimited modification of data is possible.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H. Scored by CNA (redhat.com).

Official description

A flaw was found in KubeVirt's safepath package used by virt-handler. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descriptor to a path leaf, but downstream operations resolve the path via /proc/self/fd/N using link-following syscalls. When the leaf is a symlink, the kernel dereferences it, defeating the intended no-follow protection. An attacker with access to a virt-launcher pod can exploit this to redirect virt-handler's IPC socket connections, including the notify socket used for VM domain lifecycle events. By hijacking this socket, the attacker can inject arbitrary domain events into virt-handler, causing it to take incorrect lifecycle actions, corrupt VM state in the Kubernetes API, or crash — resulting in sustained denial of VM management services for all virtual machines on the affected node. Additionally, the same symlink following flaw allows virt-handler to apply file ownership or permission changes to unintended host paths.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: UNIX Symbolic Link (Symlink) Following

The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

How developers prevent this class of flaw

  • Symbolic link attacks often occur when a program creates a tmp directory that stores files/links. Access to the directory should be restricted to the program as to prevent attackers from manipulating the files.
  • Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.

More UNIX Symbolic Link (Symlink) Following vulnerabilities (CWE-61)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Red Hat Container Native Virtualization 4.12

All Red Hat Container Native Virtualization 4.12 vulnerabilities

Recent UNIX Symbolic Link (Symlink) Following vulnerabilities

Spotted an error? Tell us.