Vulnerabilities in pkg:golang/github.com/lxc/lxd

PACKAGE
Advisory Identifier: GHSA-w2hg-2v4p-vmh6
Advisory Summary

CVE-2025-54287 is a HIGH (CVSS 6.5) canonical lxd arbitrary file read vulnerability (CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine) affecting Github.com/lxc/lxd libraries in the Go ecosystem. The issue involves canonical lxd arbitrary file read via template injection in snapshot patterns. Remediation is available by upgrading affected packages to version 5.21.4, 6.5.0, 0.0.0-20250827065555-0494f5d47e41.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/lxc/lxd

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/lxc/lxd. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-w2hg-2v4p-vmh6 CVE-2025-54287 HIGH Canonical LXD Arbitrary File Read via Template Injection in Snapshot Patterns
GHSA-8mpq-fmr3-6jxv CVE-2015-1340 HIGH LXD vulnerable to Race Condition

CVE-2025-54287 at a Glance

CVE Identifier CVE-2025-54287
GHSA Identifier GHSA-w2hg-2v4p-vmh6
Severity HIGH
CVSS v3.1 Base Score 6.5
CWE Classification CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine
Affected Product Github.com/lxc/lxd
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-54287

To remediate this vulnerability, upgrade all affected Github.com/lxc/lxd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/lxc/lxd fixed: 5.21.4
Upgrade github.com/lxc/lxd to 5.21.4
github.com/lxc/lxd fixed: 6.5.0
Upgrade github.com/lxc/lxd to 6.5.0
github.com/lxc/lxd fixed: 0.0.0-20250827065555-0494f5d47e41
Upgrade github.com/lxc/lxd to 0.0.0-20250827065555-0494f5d47e41
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/lxc/lxd

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-54287, inspect your project dependencies for Github.com/lxc/lxd:

inspect dependencies for github.com/lxc/lxd

Analyze the terminal output to locate any version of Github.com/lxc/lxd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.21.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine, where the product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine. In Github.com/lxc/lxd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 1. Log in to LXD-UI with an account that has permissions to modify instance settings 2. 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. 3. Set scheduled snapshots to run every minute and wait for snapshot generation 4. 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 ### Countermeasures Pongo2 provides mechanisms for sandboxing templates. > Template sandboxing (directory patterns, banned tags/filters) ( https://github.com/flosch/pongo2/tree/master?tab=readme-ov-file#features ) This functionality allows banning specific tags and filters by generating a custom TemplateSet. At minimum, the following tags are considered to pose a risk of file leakage on the LXD host when used. Therefore, banning these can provide countermeasures against file reading attacks. -​ include -​ ssi -​ extends -​ import The deny-list approach is prone to vulnerability recurrence due to missed countermeasures or new feature additions. Therefore, as the safest approach, we recommend using an allow-list format to permit only necessary functions. However, as far as our investigation shows, pongo2 does not have functionality to retrieve a list of registered tags or filters, nor does it provide means to implement an allow-list approach. Therefore, it is necessary to either forcibly obtain the registration list through reflection and ban anything not on the allow-list, or ban everything from the current implemented list since the library has not been updated for about two years. In LXD's implementation, template injection attacks can be prevented by modifying the `RenderTemplate` function in `shared/util.go` to use a restricted `TemplateSet` as shown above. ### Patches | 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 | ### References Reported by GMO Flatt Security Inc.

CVE-2025-54287 Affected Github.com/lxc/lxd Versions

3 component(s)
Fixed Versions:
5.21.46.5.00.0.0-20250827065555-0494f5d47e41
Product / Package Ecosystem Affected Versions Fixed Version
github.com/lxc/lxd
Go
≥ 4.0.0
< 5.21.4
5.21.4
github.com/lxc/lxd
Go
≥ 6.0.0
< 6.5.0
6.5.0
github.com/lxc/lxd
Go
≥ 0.0.0-20200331193331-03aab09f5b5c
< 0.0.0-20250827065555-0494f5d47e41
0.0.0-20250827065555-0494f5d47e41

References

Frequently Asked Questions

What is CVE-2025-54287?
CVE-2025-54287 is a security vulnerability in Github.com/lxc/lxd involving Canonical LXD Arbitrary File Read via Template Injection in Snapshot Patterns under CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine.
Which Github.com/lxc/lxd versions are affected?
Affected versions include releases prior to 5.21.4, 6.5.0, 0.0.0-20250827065555-0494f5d47e41 across affected packages: github.com/lxc/lxd.
What version fixes CVE-2025-54287?
Upgrading to 5.21.4, 6.5.0, 0.0.0-20250827065555-0494f5d47e41 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/lxc/lxd affected?
Yes, github.com/lxc/lxd is affected in releases prior to 5.21.4, 6.5.0, 0.0.0-20250827065555-0494f5d47e41. Upgrade your dependency to 5.21.4, 6.5.0, 0.0.0-20250827065555-0494f5d47e41 or later.
What is the CVSS score of CVE-2025-54287?
CVE-2025-54287 has a CVSS v3.1 base score of 6.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2025-54287?
CVE-2025-54287 is classified under CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine (The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.).
How can I check Go dependencies for CVE-2025-54287?
Run the dependency tree command: 'inspect dependencies for github.com/lxc/lxd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w2hg-2v4p-vmh6",
  "modified" : "2026-01-16T22:03:02Z",
  "published" : "2025-10-02T21:21:33Z",
  "aliases" : [ "CVE-2025-54287" ],
  "summary" : "Canonical LXD Arbitrary File Read via Template Injection in Snapshot Patterns",
  "details" : "### Impact\nIn 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.\n\n### Reproduction Steps\n\n1. Log in to LXD-UI with an account that has permissions to modify instance settings\n2. Set the following template injection payload in the instance snapshot pattern:\n\n```\n{% filter urlencode|slice:\":100\" %}{% include \"/etc/passwd\" %}{%endfilter %}\n```\n\nNote 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.\n\n3. Set scheduled snapshots to run every minute and wait for snapshot generation\n4. Wait about a minute and confirm that file contents can be obtained from the created snapshot name\n\n### Risk\nThe attack requires having configuration change permissions for LXD instances.\nThe attack allows reading arbitrary files accessible with LXD process permissions. This could lead to leakage of the following information:\n-​ LXD host configuration files (/etc/passwd, /etc/shadow, etc.)\n-​ LXD database files (containing information about all projects and instances)\n-​ Configuration files and data of other instances\n-​ Sensitive information on the host system\n\n### Countermeasures\nPongo2 provides mechanisms for sandboxing templates.\n\n> Template sandboxing (directory patterns, banned tags/filters)\n( https://github.com/flosch/pongo2/tree/master?tab=readme-ov-file#features )\n\nThis functionality allows banning specific tags and filters by generating a custom TemplateSet.\n\nAt minimum, the following tags are considered to pose a risk of file leakage on the LXD host when used. Therefore, banning these can provide countermeasures against file reading attacks.\n-​ include\n-​ ssi\n-​ extends\n-​ import\n\nThe deny-list approach is prone to vulnerability recurrence due to missed countermeasures or new feature additions. Therefore, as the safest approach, we recommend using an allow-list format to permit only necessary functions.\n\nHowever, as far as our investigation shows, pongo2 does not have functionality to retrieve a list of registered tags or filters, nor does it provide means to implement an allow-list approach. Therefore, it is necessary to either forcibly obtain the registration list through reflection and ban anything not on the allow-list, or ban everything from the current implemented list since the library has not been updated for about two years.\n\nIn LXD's implementation, template injection attacks can be prevented by modifying the `RenderTemplate` function in `shared/util.go` to use a restricted `TemplateSet` as shown above.\n\n### Patches\n\n| LXD Series  | Status |\n| ------------- | ------------- |\n| 6 | Fixed in LXD 6.5  |\n| 5.21 | Fixed in LXD 5.21.4  |\n| 5.0 | Ignored - Not critical  |\n| 4.0  | Ignored - EOL and not critical |\n\n### References\nReported by GMO Flatt Security Inc.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lxc/lxd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "5.21.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lxc/lxd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0"
      }, {
        "fixed" : "6.5.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/lxc/lxd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0-20200331193331-03aab09f5b5c"
      }, {
        "fixed" : "0.0.0-20250827065555-0494f5d47e41"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/canonical/lxd/security/advisories/GHSA-w2hg-2v4p-vmh6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-54287"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/canonical/lxd"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-4004"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1336" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-02T21:21:33Z",
    "nvd_published_at" : "2025-10-02T10:15:38Z"
  }
}