Skip to main content
Menu
CVEs

Red Hat OpenShift Virtualization authorization bypass in containerized-data-importer

CVE-2026-133879Published , updated

7.7HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Specific setups only

Summary

The containerized-data-importer component of Red Hat OpenShift Virtualization has an authorization bypass that a tenant with low-privilege access can reach remotely over the network. By creating a virtual machine with a specific annotation and a cross-namespace clone source, an attacker can copy a persistent volume claim from another namespace into their own, exposing data across tenants.

Written by a model

Original description

A flaw was found in KubeVirt/containerized-data-importer. When a VirtualMachine with an embedded DataVolumeTemplate carrying the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant, the service-account clone authorization check can be bypassed, allowing a PVC from another namespace to be cloned into the tenant's namespace without the required permissions. This can result in cross-tenant data disclosure.

Who should check

Teams running KubeVirt with containerized-data-importer on multi-tenant Red Hat OpenShift Virtualization 4 or 5 clusters where untrusted users can create VirtualMachines.

“This issue affects multi-tenant clusters running KubeVirt with containerized-data-importer where untrusted users hold VirtualMachine create permissions”

access.redhat.com

What to do

  1. Check whether your setup matches what the bug needs.

    A VirtualMachine with an embedded DataVolumeTemplate that carries the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant. Multi-tenant clusters where untrusted users hold VirtualMachine create permissions, such as through the default kubevirt.io:edit role.
  2. Workaround: Restrict VirtualMachine create/update permissions to trusted users only, or use admission policies to reject VirtualMachine DataVolumeTemplates that specify a cross-namespace clone source or carry cdi.kubevirt.io annotations affecting clone authorization.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133879 (Kubevirt: containerized-data-importer: kubevirt/cdi: cross-namespace pvc clone authorization bypass via user-controlled checkstaticvolume…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133879 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- and 23 more affected products, listed on https://cve.now/CVE-2026-133879
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- A VirtualMachine with an embedded DataVolumeTemplate that carries the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant. (source: https://access.redhat.com/security/cve/cve-2026-133879)
- Multi-tenant clusters where untrusted users hold VirtualMachine create permissions, such as through the default kubevirt.io:edit role. (source: https://access.redhat.com/security/cve/cve-2026-133879)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Restrict VirtualMachine create/update permissions to trusted users only, or use admission policies to reject VirtualMachine DataVolumeTemplates that specify a cross-namespace clone source or carry cdi.kubevirt.io annotations affecting clone authorization. (source: https://www.cve.org/CVERecord?id=CVE-2026-133879)
CISA KEV: CVE-2026-133879 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133879 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2578653
- https://access.redhat.com/security/cve/CVE-2026-133879
- https://www.cve.org/CVERecord?id=CVE-2026-133879
- https://access.redhat.com/security/cve/cve-2026-133879
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133879
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133879"}.

Affected versions

cve.now Index

31Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Shipped in major Linux distributions
  • Severity7.7/10CVSS 7.7
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 38 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133879
RecordNVD · CVE-2026-133879
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2578653
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-133879

Questions about CVE-2026-133879

Is CVE-2026-133879 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A tenant who can create VirtualMachine objects can clone a PersistentVolumeClaim from another namespace they are not authorized to access into their own namespace. This results in cross-tenant data disclosure.

Source: access.redhat.com, cve.org

Am I affected, and how do I check?

The issue affects multi-tenant clusters running KubeVirt with containerized-data-importer where untrusted users hold VirtualMachine create permissions, such as those granted by the default kubevirt.io:edit role. It requires a VirtualMachine with an embedded DataVolumeTemplate that carries the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source. Red Hat OpenShift Virtualization 4 and 5 are listed as affected products, and the advisory does not give specific version ranges.

Source: access.redhat.com, cve.org

How do I fix CVE-2026-133879?

The facts do not name a fixed version or patch ids, so no upgrade target can be given from them. Check the vendor advisory for a fix.

Source: access.redhat.com, cve.org

What if there's no patch?

Restrict VirtualMachine create and update permissions to trusted users only, for example by removing the kubevirt.io:edit role from untrusted tenants. Alternatively, use admission policies to reject VirtualMachine DataVolumeTemplates that specify a cross-namespace clone source or carry cdi.kubevirt.io annotations affecting clone authorization.

Source: access.redhat.com, cve.org

No corrections so far. Something wrong on this page? Report an error.