# CVE-2026-41012: BOSH vSphere CPI Improper Cert Validation


- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-3rqq-7767-6jq7

## What is CVE-2026-41012?

CVE-2026-41012 is a high-severity vulnerability in Cloud Foundry bosh-vsphere-cpi-release, published on 29 Aug 2026. 

### Official description

Traffic interception vulnerability in BOSH Director vCenter CPI allows attackers positioned between BOSH Director and vCenter to impersonate vCenter REST API and capture administrator credentials via HTTP Basic auth, leading to complete virtualization infrastructure takeover.

An attacker who can intercept traffic between the BOSH Director and vCenter can establish a malicious server impersonating the vCenter REST API. When the BOSH Director makes CPI calls to perform routine cloud infrastructure operations, the attacker captures the vCenter administrator username and password transmitted via HTTP Basic authentication.

The vulnerability stems from insufficient authentication security in the communication protocol between BOSH Director and vCenter. While HTTPS may be used, the lack of proper certificate validation and pinning allows attackers to successfully impersonate vCenter endpoints. Because vCenter credentials typically grant full administrative control over the entire virtualization estate, successful credential capture yields complete takeover of every VM, datastore, and network the CPI manages.

This exposure exists on every CPI call (including routine deployment operations, not just when tags are configured) and cannot be mitigated by supplying a CA certificate alone. The attack impacts all infrastructure managed by the compromised vCenter instance, potentially affecting hundreds or thousands of VMs across multiple deployments and environments.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-41012?


## How do I fix CVE-2026-41012?

No fix has been published for CVE-2026-41012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41012 being exploited?

There is no known exploitation of CVE-2026-41012 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41012 and fix it if it is affected.

What it is: CVE-2026-41012 is a high-severity vulnerability in Cloud Foundry bosh-vsphere-cpi-release, published on 29 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-41012 in the wild and no public exploit code.

Affected product: Cloud Foundry bosh-vsphere-cpi-release. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41012/ (Markdown: https://insights.sbomify.com/CVE-2026-41012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41012
- OSV: https://osv.dev/vulnerability/CVE-2026-41012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41012/
Summaries are generated and may contain mistakes; the official description above is the record.