Skip to main content
CVE-2025-54289VulnerabilityPublished Updated

CVE-2025-54289: Canonical LXD · Missing Origin Validation in WebSockets

Affects Canonical LXDSource CVE Database V5

0

Not known to be exploited · CVSS 7.4 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Canonical LXDAffected
  • =6
  • =5.21
Fixed in–

AI-suggested

To mitigate CVE-2025-54289, organizations should prioritize upgrading Canonical LXD to version 6.5 or later once patches are available. In the absence of an immediate patch, administrators should restrict read permissions to trusted users only, minimizing the number of accounts that can access the operations API. Network segmentation should be enforced to limit access to the LXD API endpoints, ideally restricting them to management networks or VPNs. Implement strict WebSocket origin validation at the network or application layer using reverse proxies or Web Application Firewalls (WAFs) that can inspect and validate WebSocket handshake headers. Monitoring and logging WebSocket connections for unusual activity can help detect attempted hijacking. Additionally, enforce multi-factor authentication (MFA) for users with any level of access to LXD to reduce the risk of credential compromise. Regularly audit user permissions and session activity to identify and revoke unnecessary read privileges. Finally, educate administrators and developers about the risks of WebSocket origin validation flaws and encourage secure coding and configuration practices.

Description

Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read permissions to hijack terminal or console sessions and execute arbitrary commands via WebSocket connection hijacking format

References

Community reviews

Loading reviews…