Quick answers
- Is CVE-2026-16792 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16792 being exploited in the wild.
- How severe is CVE-2026-16792?
- Medium severity, with a CVSS score of 6.1, published 4 August 2026.
- Which products and versions are affected?
- Lenovo XClarity Orchestrator 2.2.0.
- Is there a fix for CVE-2026-16792?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-16792 attacked?
- It is attacked from the adjacent network or over the network, in a network appliance.
- Am I affected by CVE-2026-16792?
- Check whether you run Lenovo XClarity Orchestrator at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper certificate validation flaw affecting multiple microservices in LXCO 2.2.0. The root cause involves insufficient validation of TLS certificates during HTTPS connections, which an adjacent network attacker can exploit to perform a man-in-the-middle attack. The attack requires the attacker to be on the same network segment or adjacent network and does not require prior authentication. Successful exploitation allows interception and potential modification of encrypted management traffic. Patches or mitigations were available as of the publication date (August 2026).
Affected products
- Lenovo XClarity Orchestrator 2.2.0
Timeline
- 2026-08-04: disclosed