CVE Alert: CVE-2025-8557 – Lenovo – XClarity Orchestrator (LXCO)

CVE-2025-8557

HIGHNo exploitation known

An internal product security audit of Lenovo XClarity Orchestrator (LXCO) discovered the below vulnerability: An attacker with access to a device on the local Lenovo XClarity Orchestrator (LXCO) network segment may be able to manipulate the local device to create an alternate communication channel which could allow the attacker, under certain conditions, to directly interact with backend LXCO API services typically inaccessible to users. While access controls may limit the scope of interaction, this could result in unauthorized access to internal functionality or data. This issue is not exploitable from remote networks.

CVSS v3.1 (8.8)
AV ADJACENT_NETWORK · AC LOW · PR NONE · UI NONE · S UNCHANGED
Vendor
Lenovo
Product
XClarity Orchestrator (LXCO)
Versions
0 lt 2.2.0
CWE
CWE-420, CWE-420: Unprotected Alternate Channel
Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2025-09-11T18:34:27.875Z
Updated
2025-09-11T18:56:07.128Z

AI Summary Analysis

Risk verdict

High risk, given the high impact potential and the need for local network access; not reachable from the internet.

Why this matters

An attacker on the LXCO network could manipulate a device to access backend API services normally restricted to authorised users, potentially exposing or altering internal data and functionality. The combination of high confidentiality and integrity impact with no user interaction elevates risk for insider threats or compromised admin networks.

Most likely attack path

Attacker already on the same local network segment; no privileges or user interaction required. They could coax a local device to establish or divert communications to backend APIs, effectively bypassing standard access controls. Exploitation hinges on adjacent-network access and untrusted channels rather than remote internet access.

Who is most exposed

Environments where LXCO sits on enterprise management networks or data-centre admin VLANs, often with broad local access for IT staff, and where network segmentation is imperfect.

Detection ideas

  • Unusual internal API call patterns from non-admin devices.
  • New or unexpected internal communications channels to LXCO APIs.
  • Anomalous port or protocol usage within the management network.
  • Authentication anomalies for internal API endpoints or elevated access attempts.

Mitigation and prioritisation

  • Patch to version 2.2.0 or higher immediately.
  • Strengthen network segmentation; restrict LXCO management access to authorised hosts only.
  • Disable or closely monitor alternate-channel functionality; block non-approved internal connections.
  • Enhance logging and implement targeted alerts for internal API access and abnormal channels.
  • Coordinate change-management: test in staging, schedule controlled production rollout with backups and rollback plans.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.