CVE-2026-13622: Kubevirt: virt-handler-rhel9: kubevirt: virt-handler migration proxy follows symlinks allowing container escape to host
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 1.8.4-4; azl3 kubevirt-openvmm 1.9.0-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 1.8.4-4; azl3 kubevirt-openvmm 1.9.0-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 12, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-22
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat Container Native Virtualization 4.12
- 1785837722 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.13
- 1786346596 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.14
- 1786309624 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.15
- 1786347656 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.16
- 1786030071 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.17
- 1786348529 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.18
- 1786130068 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.19
- 1786334215 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.20
- 1785831334 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.21
- 1785829701 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.22
- 1785140336 and laternot affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 16.0 | kubevirt1.8 | before 1.8.4-160000.1.1 | 1.8.4-160000.1.1 |
| openSUSE:Leap 16.0 | kubevirt1.9 | before 1.9.1-160000.1.1 | 1.9.1-160000.1.1 |
| openSUSE:Tumbleweed | kubevirt1.8 | before 1.8.4-6.1 | 1.8.4-6.1 |
| openSUSE:Tumbleweed | kubevirt1.9 | before 1.9.0-3.1 | 1.9.0-3.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP7 | kubevirt | before 1.7.4-150700.3.36.1 | 1.7.4-150700.3.36.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP7 | kubevirt-1.6 | before 1.6.6-150700.15.17.1 | 1.6.6-150700.15.17.1 |
Same product
red hat: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-7374Kubevirt: kubevirt virt-handler: privilege escalation and node compromise via symlink following vulnerability39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 kubevirt 1.8.4-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 | 1.8.4-4 · Release Notes | Microsoft (MSRC) |
| azl3 kubevirt-openvmm 1.9.0-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| opensuse:kubevirt1.8 | 1.8.4-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kubevirt1.8 | 1.8.4-6.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kubevirt1.9 | 1.9.0-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:kubevirt | 1.7.4-150700.3.36.1 · SUSE:Linux Enterprise Module for Containers 15 SP7 | Package registry (OSV) |
| suse:kubevirt-1.6 | 1.6.6-150700.15.17.1 · SUSE:Linux Enterprise Module for Containers 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- access.redhat.com/errata/RHSA-2026:51031
- access.redhat.com/errata/RHSA-2026:53655
- access.redhat.com/errata/RHSA-2026:53671
- access.redhat.com/errata/RHSA-2026:53684
- access.redhat.com/errata/RHSA-2026:53721
- access.redhat.com/errata/RHSA-2026:53728
- access.redhat.com/errata/RHSA-2026:53763
- access.redhat.com/errata/RHSA-2026:53797
- access.redhat.com/errata/RHSA-2026:53826
- access.redhat.com/errata/RHSA-2026:53838
- access.redhat.com/security/cve/CVE-2026-13622
- bugzilla.redhat.com/show_bug.cgi?id=2494142
Vendor advisories and official records. Exploit/PoC links are deliberately left out.