GPU VulnDB

Database/Kernel, userspace & hypervisor

VMware Tools for Windows: improper authorisation lets a guest user reach other guest VMs on the same vCenter or ESX

CVSS 7.6CVE-2025-41246Kernel, userspace & hypervisorcurated

Impact

A non-administrative user inside a Windows guest who is already authenticated to vCenter or ESX can use VMware Tools to operate against other guest VMs instead of only their own. On a shared virtualized fleet that is a tenant-boundary crossing: the isolation an operator sells is per-VM, and this lets one VM's occupant act inside another. Exploitation still requires valid credentials for the target VMs and for vCenter or ESX, which is what keeps the score below critical. The flaw is in the guest agent, not the hypervisor itself, so it does not by itself yield host compromise.

Who can reach it

A local, non-administrative user in a Windows guest who also holds vCenter or ESX credentials and credentials for the targeted VMs. Authentication is required at every step.

What to do

Update VMware Tools in the affected Windows guests to the fixed release listed in the Broadcom advisory; this is a per-guest agent update, and VMware Tools upgrades on Windows commonly require a guest reboot, so plan it as a tenant-visible restart rather than a host maintenance window. No host or hypervisor change is called for. Confirm the exact fixed build against the advisory before scheduling, since the record here does not state it.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.