GPU VulnDB

Database/Kernel, userspace & hypervisor

VMware NSX: unauthenticated username enumeration through the password-recovery and login paths

CVSS 8.1CVE-2025-41251Kernel, userspace & hypervisor+1 more CVEscurated

Impact

An unauthenticated attacker who can reach the NSX manager interface can confirm which usernames are valid, turning a blind credential-stuffing attempt into a targeted brute force against the network-virtualization control plane. NSX defines the segments, firewall rules and overlay that separate tenants on a virtualized fleet, so an account that is eventually guessed is an account that can re-wire tenant isolation. The flaw itself discloses only account names - no access is granted by it. Broadcom split this across two ids (CVE-2025-41251, CVE-2025-41252) covering the weak password-recovery mechanism and the login-path enumeration; both carry the same advisory, the same fixed builds and the same operator action.

Who can reach it

Anyone with network reach to the NSX manager web interface, including anyone on the management VLAN. No authentication required.

What to do

Upgrade to NSX 9.0.1.0, 4.2.2.2/4.2.3.1 or 4.1.2.7, NSX-T 3.2.4.3, or apply the VMware Cloud Foundation async patch per KB88287. Broadcom lists no workaround, so patching is the only fix; the work is an NSX manager appliance upgrade in a maintenance window rather than anything that touches GPU hosts. Until then, keep the NSX manager off any routable network and in front of an SSO or VPN gate so the endpoints are not reachable unauthenticated.

Also covers 1 CVE

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

CVE-2025-41252

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.