# CVE-2025-54289: Privilege Escalation via WebSocket Connection Hijacking in LXD Operations API > Attackers with read permissions can hijack WebSocket sessions to execute arbitrary commands, leading to privilege escalation in LXD. - **Severity:** High 7.4 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 2 Oct 2025 - **Updated:** 26 Feb 2026 - **Also known as:** DEBIAN-CVE-2025-54289, GHSA-3g72-chj4-2228, GO-2025-3999, UBUNTU-CVE-2025-54289 ## What is CVE-2025-54289? CVE-2025-54289 is a high-severity vulnerability in Canonical LXD, published on 2 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official 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 Weakness: CWE-1385 (Missing Origin Validation in WebSockets) ## Which versions are affected by CVE-2025-54289? 7 open source packages ship an affected version, including github.com/canonical/lxd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/canonical/lxd` | Go | All versions | None | | `github.com/canonical/lxd` | Go | From 0.0.0-20200331193331-03aab09f5b5c | 0.0.0-20250827065555-0494f5d47e41 | | `github.com/canonical/lxd` | Go | From 0.0.0-20200331193331-03aab09f5b5c | 0.0.0-20250827065555-0494f5d47e41 | | `github.com/canonical/lxd` | Go | From 4.0 | 5.21.4 | | `github.com/canonical/lxd` | Go | From 4.0 | 5.21.4 | | `github.com/canonical/lxd` | Go | From 6.0 | 6.5 | | `github.com/canonical/lxd` | Go | From 6.0 | 6.5 | Products: Canonical Lxd. ## How do I fix CVE-2025-54289? Upgrade github.com/canonical/lxd to a fixed version for your release line: 0.0.0-20250827065555-0494f5d47e41, 5.21.4 or 6.5. ## Is CVE-2025-54289 being exploited? There is no known exploitation of CVE-2025-54289 in the wild and no public exploit code. ## Other vulnerabilities in Canonical LXD - [CVE-2026-66897](https://insights.sbomify.com/CVE-2026-66897/): Instance template path traversal allows arbitrary host file write as root (critical 9.9) - [CVE-2026-62420](https://insights.sbomify.com/CVE-2026-62420/): Cross-project cluster migration bypasses project restrictions via cluster notification flag (critical 9.9) - [CVE-2026-63293](https://insights.sbomify.com/CVE-2026-63293/): Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root (critical 9.9) - [CVE-2026-63294](https://insights.sbomify.com/CVE-2026-63294/): Root RCE via image backup.yaml symlink (critical 9.9) - [CVE-2026-63296](https://insights.sbomify.com/CVE-2026-63296/): Project restriction bypass via instance migration config override (critical 9.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-54289 and fix it if it is affected. What it is: CVE-2025-54289 is a high-severity vulnerability in Canonical LXD, published on 2 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-54289 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/canonical/lxd (Go): affected all versions; no fix listed - github.com/canonical/lxd (Go): affected from 0.0.0-20200331193331-03aab09f5b5c; fixed in 0.0.0-20250827065555-0494f5d47e41 - github.com/canonical/lxd (Go): affected from 0.0.0-20200331193331-03aab09f5b5c; fixed in 0.0.0-20250827065555-0494f5d47e41 - github.com/canonical/lxd (Go): affected from 4.0; fixed in 5.21.4 - github.com/canonical/lxd (Go): affected from 4.0; fixed in 5.21.4 - github.com/canonical/lxd (Go): affected from 6.0; fixed in 6.5 - github.com/canonical/lxd (Go): affected from 6.0; fixed in 6.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-54289/ (Markdown: https://insights.sbomify.com/CVE-2025-54289/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54289 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54289 - OSV: https://osv.dev/vulnerability/CVE-2025-54289 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54289/ Summaries are generated and may contain mistakes; the official description above is the record.