GPU VulnDB

Database/Control plane, storage & DevOps

BOSH vSphere CPI: missing certificate pinning lets an interceptor impersonate vCenter and capture admin credentials

CVE-2026-41012Control plane, storage & DevOpscurated

Impact

The CPI authenticates to the vCenter REST API with HTTP Basic credentials but does not properly validate or pin the server certificate, so anyone positioned on the path between the BOSH Director and vCenter can stand up an impersonating endpoint and read the vCenter administrator username and password in the clear. Those credentials normally carry full administrative control of the virtualization estate, which means every VM, datastore, and network the CPI manages - including any GPU-passthrough or vGPU-backed VMs - falls to the attacker. The advisory states the exposure occurs on every CPI call during routine deployment operations, not only in a narrow configuration, and that supplying a CA certificate alone does not mitigate it.

Who can reach it

An attacker able to intercept or redirect traffic between the BOSH Director and vCenter - in practice someone with a position on the management network segment carrying that path. No prior authentication to either endpoint is needed.

What to do

Apply the fixed bosh-vsphere-cpi-release identified in the Cloud Foundry advisory and redeploy the Director so the CPI picks it up; the NVD record names no fixed version, so take it from the advisory. Treat the vCenter credentials used by the CPI as exposed and rotate them after patching. Until then, ensure the Director-to-vCenter path does not traverse any segment an attacker could occupy - a CA certificate alone is explicitly not a mitigation.

References

Related entries

All Control plane, storage & DevOps 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.