# CVE-2026-16792: Global TLS Certificate Validation Bypass in Lenovo XClarity Orchestrator

> An attacker can intercept sensitive communications via machine-in-the-middle attacks due to improper TLS certificate validation in Lenovo XClarity Orchestrator.

- **Severity:** High 7.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-hqj6-mx68-28jm

## What is CVE-2026-16792?

CVE-2026-16792 is a high-severity vulnerability in Lenovo XClarity Orchestrator, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper certificate validation vulnerability was reported in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices that could allow an adjacent network attacker to intercept sensitive communications by performing a machine-in-the-middle attack against HTTPS connections during TLS certificate validation under certain circumstances.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-16792 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16792 is a high-severity vulnerability in Lenovo XClarity Orchestrator, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16792 in the wild and no public exploit code.

Affected product: Lenovo XClarity Orchestrator. 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-16792/ (Markdown: https://insights.sbomify.com/CVE-2026-16792/index.md)
```

## Sources

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

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