Analyst readout for executives and security teams
Plain-English summary
This flaw lets a namespace-level attacker use a symlink in an exported PVC to read files from the KubeVirt exporter pod. The known impact is sensitive information disclosure, not data modification or service outage. The source bundle identifies Red Hat OpenShift Virtualization 4 as affected.
Executive priority
Treat as high priority for OpenShift Virtualization environments because it can expose sensitive pod filesystem data from a low-privilege namespace position. Prioritize inventory, RBAC restriction, and vendor update tracking.
Technical view
CVE-2026-9804 is a CWE-59 symlink/path traversal issue in KubeVirt virt-exportserver’s VMExport directory endpoint. With low privileges and no user interaction, an attacker can escape the intended exported filesystem mount root and read arbitrary files from the exporter pod filesystem. CVSS is 7.7 high with confidentiality impact only.
Likely exposure
Exposure is most likely in Red Hat OpenShift Virtualization 4 environments using container-native-virtualization virt-exportserver or virt-exportserver-rhel9, especially where namespace users can write exported PVC contents and use VMExport functionality.
Exploitation context
The bundle does not report active exploitation, and CISA KEV status is false. Exploitation requires specific namespace-level access and a symlink placed inside an exported filesystem PVC. Evidence supports file read from the exporter pod only.
Researcher notes
The public bundle names the vulnerable component and attack condition but does not provide fixed versions, patch commits, or real-world exploitation evidence. Validation should focus on installed Red Hat OpenShift Virtualization 4 builds, VMExport use, and namespace privilege boundaries.
Mitigation direction
- Check Red Hat CVE and Bugzilla pages for fixed builds or official mitigation guidance.
- Limit VMExport creation and PVC write access to trusted namespace roles.
- Avoid exporting PVC filesystems controlled by untrusted users until vendor remediation is applied.
- Review RBAC for users who can manage VMExport resources and exported PVCs.
- Monitor exporter pod logs for unusual export requests or filesystem access errors.
Validation and detection
- Inventory clusters running Red Hat OpenShift Virtualization 4.
- Identify deployments using container-native-virtualization virt-exportserver or virt-exportserver-rhel9.
- Review namespaces where users can write PVC contents and initiate VMExport operations.
- Confirm whether Red Hat has published fixed package versions for your installed build.
- Document compensating RBAC restrictions until an official fix is applied.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9804 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N 3.1 4 redhat Vulnerability scoring details
Base CVSS 3.1 score
7.7 HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline redhat
Reported to Red Hat.
- Source timeline redhat
Made public.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://access.redhat.com/security/cve/CVE-2026-9804 CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2482487 CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.