# CVE-2025-58126: Lack of TLS validation in plugin VMware vSAN on Checkmk Exchange

> Attackers in a Man-in-the-Middle position can intercept traffic due to missing TLS validation in the Checkmk VMware vSAN plugin.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-c8gv-x3r9-q7p4

## What is CVE-2025-58126?

CVE-2025-58126 is a medium-severity vulnerability in tomtretbar:vmware_vsan, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Certificate Validation in Checkmk Exchange plugin VMware vSAN allows attackers in MitM position to intercept traffic.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-58126?

It affects 1 product.


Products: Tomtretbar Vmware Vsan.

## How do I fix CVE-2025-58126?

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

## Is CVE-2025-58126 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58126 and fix it if it is affected.

What it is: CVE-2025-58126 is a medium-severity vulnerability in tomtretbar:vmware_vsan, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58126 in the wild and no public exploit code.

Affected product: tomtretbar:vmware_vsan. 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-2025-58126/ (Markdown: https://insights.sbomify.com/CVE-2025-58126/index.md)
```

## Sources

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

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