Vulnerability in github.com/lxc/lxd (CVE-2025-54287)
Summary
Vulnerability in github.com/lxc/lxd (CVE-2025-54287). Confidential information can be exposed externally. Exploitable via snapshots.pattern. Mitigation: upgrade to 0.0.0-20250827065555-0494f5d47e41 or later.
Original description
The description as published by the source.
Impact
In LXD's instance snapshot creation functionality, the Pongo2 template engine is used in the snapshots.pattern configuration for generating snapshot names. While code execution functionality has not been found in this template engine, it has file reading capabilities, creating a vulnerability that allows arbitrary file reading through template injection attacks.
Reproduction Steps
- Log in to LXD-UI with an account that has permissions to modify instance settings
- Set the following template injection payload in the instance snapshot pattern:
{% filter urlencode|slice:":100" %}{% include "/etc/passwd" %}{%endfilter %}
Note that the above template uses the Pongo2 template engine's include tag to read system files. It also uses urlencode and slice filters to bypass character count and type restrictions.
- Set scheduled snapshots to run every minute and wait for snapshot generation
- Wait about a minute and confirm that file contents can be obtained from the created snapshot name
Risk
The attack requires having configuration change permissions for LXD instances.
The attack allows reading arbitrary files accessible with LXD process permissions. This could lead to leakage of the following information:
- LXD host configuration files (/etc/passwd, /etc/shadow, etc.)
- LXD database files (containing information about all projects and instances)
- Configuration files and data of other instances
- Sensitive information on the host system
###…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-54287 has been found in github.com/lxc/lxd.
Attackers can target a specific entry point like snapshots.pattern over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade github.com/lxc/lxd to 0.0.0-20250827065555-0494f5d47e41 or later.
If unsure, ask your IT team or search "github.com/lxc/lxd CVE-2025-54287" on the vendor's site.
CVE-2025-54287 (github.com/lxc/lxd) — CWE-1336 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: snapshots.pattern / RenderTemplate / TemplateSet
Patched: 0.0.0-20250827065555-0494f5d47e41 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1336) exists in github.com/lxc/lxd. Attackers reach the vulnerable code path via snapshots.pattern.
Check the vendor advisory for the affected versions of github.com/lxc/lxd. Attack surface: snapshots.pattern / RenderTemplate / TemplateSet.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 0.0.0-20250827065555-0494f5d47e41.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/lxc/lxd' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/lxc/lxd' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/lxc/lxdを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/lxc/lxd to 0.0.0-20250827065555-0494f5d47e41ステージング環境で 0.0.0-20250827065555-0494f5d47e41 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-54287 incus Fixed in: 6.0.4-2+deb13u1
References
- advisory nvd.nist.gov
- exploit github.com
- package github.com
- web pkg.go.dev