Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Adjacent-only vector; AC:H for unspecified triggering conditions; scope changed because subsequent system confidentiality is also impacted per SC:H in the 4.0 vector.
Primary rating from Vendor (lenovo).
CVSS VectorVendor: lenovo
Lifecycle Timeline
4DescriptionCVE.org
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.
AnalysisAI
Improper TLS certificate validation in multiple Lenovo XClarity Orchestrator (LXCO) 2.2.0 microservices exposes sensitive management communications to interception by an adjacent network attacker capable of positioning themselves for a machine-in-the-middle attack. The flaw (CWE-295) allows the attacker to bypass HTTPS trust enforcement under unspecified triggering circumstances, potentially capturing credentials, tokens, or orchestration data exchanged between LXCO microservices. No public exploit code or CISA KEV listing exists at time of analysis; Lenovo has released a patch via advisory HT509976.
Technical ContextAI
Lenovo XClarity Orchestrator is an enterprise data center infrastructure management platform that coordinates Lenovo ThinkSystem and ThinkAgile hardware through a microservices architecture. The vulnerability stems from CWE-295 (Improper Certificate Validation), a class of flaw where TLS handshake logic fails to correctly verify the authenticity of a peer's X.509 certificate - enabling an attacker controlling the network path to present a forged certificate without rejection. Because LXCO is composed of multiple loosely-coupled microservices that communicate internally over HTTPS, a single point of certificate validation failure can expose inter-service traffic, not merely end-user sessions. The CPE (cpe:2.3:a:lenovo:xclarity_orchestrator:*:*:*:*:*:*:*:*) uses a wildcard version, suggesting NVD has not yet bounded the affected version range beyond the vendor-disclosed 2.2.0 baseline.
RemediationAI
Apply the vendor-released patch per Lenovo Security Advisory HT509976, available at https://support.lenovo.com/my/en/solutions/ht509976-lenovo-xclarity-orchestrator. The exact patched version number is not specified in available intelligence sources and must be confirmed by consulting the advisory directly - do not assume a specific version without verifying. As a compensating control pending patching, restrict network adjacency to LXCO management interfaces by placing LXCO nodes on a dedicated, isolated management VLAN accessible only to authorized administrators; this eliminates the adjacent-network attack surface required by AV:A. Additionally, enforce strict network ACLs on switch infrastructure serving the LXCO segment to prevent unauthorized devices from joining that broadcast domain. These controls reduce exploitation opportunity but do not remediate the underlying certificate validation defect.
More in Xclarity Orchestrator
View allOS command injection in Lenovo XClarity Orchestrator (LXCO) 2.2.0 enables an authenticated low-privileged attacker to ex
An internal product security audit of LXCO, prior to version 1.2.2, discovered that credentials for Lenovo XClarity Admi
Same weakness CWE-295 – Improper Certificate Validation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-52885
GHSA-hqj6-mx68-28jm