cve.bz

CVE-2026-13201 UNIX Symbolic Link (Symlink) Following

7.3 highEPSS 0.3%Fix available

High (7.3). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat Container Native Virtualization 4.12: fixed in 1791522624
  • Red Hat Red Hat Container Native Virtualization 4.13: fixed in 1786346596
  • Red Hat Red Hat Container Native Virtualization 4.14: fixed in 1786309624
  • Red Hat Red Hat Container Native Virtualization 4.15: fixed in 1786347656
  • Red Hat Red Hat Container Native Virtualization 4.16: fixed in 1786030071
  • Red Hat Red Hat Container Native Virtualization 4.17: fixed in 1786348529
  • Red Hat Red Hat Container Native Virtualization 4.18: fixed in 1786130068
  • Red Hat Red Hat Container Native Virtualization 4.19: fixed in 1786334215
  • SUSE, openSUSE, Azure Linux: fixed package versions per release
  • Vendor advisory: https://access.redhat.com/security/cve/CVE-2026-13201
  • Vendor advisory: https://bugzilla.redhat.com/show_bug.cgi?id=2492203

Ask an AI about this CVE

Show the promptExplain CVE-2026-13201 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-13201?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-13201?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-13201 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-13201

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-13201](https://cve.bz/cve/badge/CVE-2026-13201.svg)](https://cve.bz/cve/CVE-2026-13201)

HTML:

<a href="https://cve.bz/cve/CVE-2026-13201"><img src="https://cve.bz/cve/badge/CVE-2026-13201.svg" alt="CVE-2026-13201"></a>

Affected

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat Container Native Virtualization 4.121791522624
Red Hat Container Native Virtualization 4.131786346596
Red Hat Container Native Virtualization 4.141786309624
Red Hat Container Native Virtualization 4.151786347656
Red Hat Container Native Virtualization 4.161786030071
Red Hat Container Native Virtualization 4.171786348529
Red Hat Container Native Virtualization 4.181786130068
Red Hat Container Native Virtualization 4.191786334215
Red Hat Container Native Virtualization 4.201785831334
Red Hat Container Native Virtualization 4.211785829701
Red Hat Container Native Virtualization 4.221785140336

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Module for Containers 15 SP7kubevirt1.7.4-150700.3.33.1SUSE-SU-2026:3480-1
SUSELinux Enterprise Module for Containers 15 SP7kubevirt-1.61.6.6-150700.15.17.1SUSE-SU-2026:3630-1
openSUSELeap 16.0kubevirt1.81.8.4-160000.1.1openSUSE-SU-2026:21590-1
openSUSETumbleweedkubevirt1.81.8.4-3.1openSUSE-SU-2026:11392-1
openSUSETumbleweedkubevirt1.91.9.0-1.1openSUSE-SU-2026:11520-1
Azure Linux3kubevirt1.8.4-4AZL-91173

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in KubeVirt's safepath package where OpenAtNoFollow obtains a file descriptor to a leaf symlink using O_PATH|O_NOFOLLOW, then downstream operations resolve the path via /proc/self/fd/N which dereferences the symlink, defeating the intended no-follow protection.

The primary impact is through notify socket hijacking: virt-handler uses safepath to resolve the path to the notify socket inside each virt-launcher pod. A namespace-level tenant with pod access can replace this socket path with a symlink to an attacker-controlled socket, enabling injection of arbitrary VM domain lifecycle events. Since virt-handler treats this as a trusted IPC channel, injected events are processed without validation and propagated to the Kubernetes API as VMI status updates. This allows the attacker to trigger incorrect VM lifecycle actions (shutdowns, restarts, migrations), corrupt VMI resource state, or crash the virt-handler process through malformed events. Because virt-handler is a single DaemonSet pod per node, a sustained crash loop denies VM management services — including console access, live migration, and lifecycle operations — for all virtual machines on that node.

A secondary impact exists through the chown/chmod path: virt-handler (running as root on the node) can be tricked into applying file ownership or permission changes to arbitrary host files with hardcoded values. This modification is blind — the attacker cannot read or write file contents and remains confined to the container. In default OpenShift Virtualization deployments, SELinux mandatory access controls and RHCOS immutable filesystem layers limit the set of targetable host files.

Red Hat's mitigation

The following measures reduce the attacker pool and limit secondary impact:

Review RBAC policies to restrict pods/exec permissions on virt-launcher pods to only those users who strictly require it. This reduces the number of identities that can place symlinks in the launcher filesystem.

Ensure SELinux is in enforcing mode (default in OpenShift). While SELinux does not prevent the notify socket hijacking path, it restricts the set of host files targetable through the chown/chmod path by blocking operations on files with protected security labels.

RHCOS immutable filesystem layers prevent modification of core OS files through the chown/chmod path.

Note: no mitigation currently addresses the notify socket hijacking vector. The attacker's ability to inject domain events into virt-handler is not constrained by SELinux or filesystem immutability.

ProductPackageStateAdvisory
Red Hat Container Native Virtualization 4.12container-native-virtualization/virt-handler:1791522624Fixed 2026-10-12RHSA-2026:80941
Red Hat Container Native Virtualization 4.13container-native-virtualization/virt-handler-rhel9:1786346596Fixed 2026-08-11RHSA-2026:53655
Red Hat Container Native Virtualization 4.14container-native-virtualization/virt-handler-rhel9:1786309624Fixed 2026-08-11RHSA-2026:53671
Red Hat Container Native Virtualization 4.15container-native-virtualization/virt-handler-rhel9:1786347656Fixed 2026-08-11RHSA-2026:53826
Red Hat Container Native Virtualization 4.16container-native-virtualization/virt-handler-rhel9:1786030071Fixed 2026-08-11RHSA-2026:53721
Red Hat Container Native Virtualization 4.17container-native-virtualization/virt-handler-rhel9:1786348529Fixed 2026-08-11RHSA-2026:53684
Red Hat Container Native Virtualization 4.18container-native-virtualization/virt-handler-rhel9:1786130068Fixed 2026-08-11RHSA-2026:53838
Red Hat Container Native Virtualization 4.19container-native-virtualization/virt-handler-rhel9:1786334215Fixed 2026-08-11RHSA-2026:53797
Red Hat Container Native Virtualization 4.20container-native-virtualization/virt-handler-rhel9:1785831334Fixed 2026-08-11RHSA-2026:53763
Red Hat Container Native Virtualization 4.21container-native-virtualization/virt-handler-rhel9:1785829701Fixed 2026-08-11RHSA-2026:53728
Red Hat Container Native Virtualization 4.22container-native-virtualization/virt-handler-rhel9:1785140336Fixed 2026-08-06RHSA-2026:51031

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-13201.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON