Summary
Canonical LXD Vulnerable to Privilege Escalation via WebSocket Connection Hijacking in Operations API
Impact
LXD's operations API includes secret values necessary for WebSocket connections when retrieving information about running operations. These secret values are used for authentication of WebSocket connections for terminal and console sessions.
Therefore, attackers with only read permissions can use secret values obtained from the operations API to hijack terminal or console sessions opened by other users. Through this hijacking, attackers can execute arbitrary commands inside instances with the victim's privileges.
CVE-2025-54289 has a CVSS score of 6.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.21.4, 6.5, 0.0.0-20250827065555-0494f5d47e41); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
| LXD Series | Status |
|---|---|
| 6 | Fixed in LXD 6.5 |
| 5.21 | Fixed in LXD 5.21.4 |
| 5.0 | Ignored - Not critical |
| 4.0 | Ignored - EOL and not critical |
Frequently Asked Questions
- What is CVE-2025-54289? CVE-2025-54289 is a high-severity security vulnerability in github.com/canonical/lxd (go), affecting versions >= 4.0, < 5.21.4. It is fixed in 5.21.4, 6.5, 0.0.0-20250827065555-0494f5d47e41.
- How severe is CVE-2025-54289? CVE-2025-54289 has a CVSS score of 6.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/canonical/lxd are affected by CVE-2025-54289? github.com/canonical/lxd (go) versions >= 4.0, < 5.21.4 is affected.
- Is there a fix for CVE-2025-54289? Yes. CVE-2025-54289 is fixed in 5.21.4, 6.5, 0.0.0-20250827065555-0494f5d47e41. Upgrade to this version or later.
- Is CVE-2025-54289 exploitable, and should I be worried? Whether CVE-2025-54289 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-54289 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-54289?
- Upgrade
github.com/canonical/lxdto 5.21.4 or later - Upgrade
github.com/canonical/lxdto 6.5 or later - Upgrade
github.com/canonical/lxdto 0.0.0-20250827065555-0494f5d47e41 or later
- Upgrade