CVE-2026-9804: Kubevirt: kubevirt: vmexport directory symlink escape enables exporter pod file read
Noroxi assessment
Priority: Monitor (action score 30/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.51% (FIRST EPSS).
- Anyone who can reach it over the internet 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.7.1-8 on Azure Linux 3.0 1.8.4-1.
Low priority for now. Upgrade to azl3 kubevirt 1.7.1-8 on Azure Linux 3.0 1.8.4-1 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 flaw was found in KubeVirt's virt-exportserver component. An attacker with specific namespace-level access can exploit a path traversal vulnerability in the VMExport directory endpoint. By placing a symbolic link (symlink) within an exported filesystem Persistent Volume Claim (PVC) that points outside its designated mount root, the attacker can read arbitrary files from the exporter pod's filesystem. This leads to information disclosure, potentially exposing sensitive data.
- Published
- May 28, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-59
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 7.7
- 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.
| Vendor | Product | CPE |
|---|---|---|
| container native virtualization | 4.17 | cpe:2.3:redhat:container_native_virtualization:4.17 |
| container native virtualization | 4.18 | cpe:2.3:redhat:container_native_virtualization:4.18 |
| container native virtualization | 4.19 | cpe:2.3:redhat:container_native_virtualization:4.19 |
| container native virtualization | 4.20 | cpe:2.3:redhat:container_native_virtualization:4.20 |
| container native virtualization | 4.21 | cpe:2.3:redhat:container_native_virtualization:4.21 |
| container native virtualization | 4 | cpe:2.3:redhat:container_native_virtualization:4 |
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.17
- 1781757410 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.18
- 1781928221 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.19
- 1781590993 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.20
- 1781838712 and laternot affected · rpm
Red Hat Red Hat Container Native Virtualization 4.21
- 1782012918 and laternot affected · rpm
Red Hat Red Hat OpenShift Virtualization 4
- all versionsaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | kubevirt.io/kubevirt | from 0 | — |
| Go | kubevirt.io/kubevirt | up to and including 1.9.0-beta.0 | — |
| openSUSE:Tumbleweed | kubevirt | before 1.8.3-1.1 | 1.8.3-1.1 |
| openSUSE:Tumbleweed | kubevirt-1.8 | before 1.8.3-1.1 | 1.8.3-1.1 |
| openSUSE:Tumbleweed | kubevirt1.8 | before 1.8.3-1.1 | 1.8.3-1.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP7 | kubevirt | before 1.7.4-150700.3.27.1 | 1.7.4-150700.3.27.1 |
| SUSE:Linux Enterprise Module for Containers 15 SP7 | kubevirt-1.6 | before 1.6.6-150700.15.10.1 | 1.6.6-150700.15.10.1 |
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.7.1-8 on Azure Linux 3.0 | 1.8.4-1 | Microsoft (MSRC) |
| opensuse:kubevirt | 1.8.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kubevirt-1.8 | 1.8.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kubevirt1.8 | 1.8.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:kubevirt | 1.7.4-150700.3.27.1 · SUSE:Linux Enterprise Module for Containers 15 SP7 | Package registry (OSV) |
| suse:kubevirt-1.6 | 1.6.6-150700.15.10.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.
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: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
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)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- access.redhat.com/errata/RHSA-2026:27913
- access.redhat.com/errata/RHSA-2026:27914
- access.redhat.com/errata/RHSA-2026:27983
- access.redhat.com/errata/RHSA-2026:28002
- access.redhat.com/security/cve/CVE-2026-9804
- bugzilla.redhat.com/show_bug.cgi?id=2482487
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-9804.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.