Incus is a system container and virtual machine manager. Prior to version 7.0.0, backup.GetInfo() trusts the inline backup/index.yaml config when present and only falls back to parsing the legacy backup/container/backup.yaml file if result.Config == nil. As a result, an archive can carry a valid inline config that passes the initial import preflight while also carrying a malformed legacy backup/container/backup.yaml file that is reparsed later from the restored file system. ParseConfigYamlFile() accepts YAML documents with no container section, and multiple downstream consumers then dereference. Container without checking for nil. Confirmed examples in the instance restore and import flow include backup.UpdateInstanceConfig() and internalImportFromBackup(). An authenticated user with permission to import instance backups may be able to crash the Incus daemon with a crafted backup archive whose inline backup/index.yaml is valid but whose extracted legacy backup.yaml omits container. The crash occurs in the restore path after archive extraction has begun. This issue has been patched in version 7.0.0.

The remote host is affected by the vulnerability described in GLSA-202608-23 (Incus: Multiple Vulnerabilities)

    Multiple vulnerabilities have been discovered in Incus. Please review the CVE identifiers referenced below     for details.

Tenable has extracted the preceding description block directly from the Gentoo Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 12 / 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6247 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6247-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     May 04, 2026                          https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : lxd     CVE ID         : CVE-2026-40197 CVE-2026-40251 CVE-2026-41648                      CVE-2026-41684 CVE-2026-41685

    Multiple security issues were discovered in LXD, a system container     and virtual machine manager, which could result in denial of service.

    For the oldstable distribution (bookworm), these problems have been fixed     in version 5.0.2-5+deb12u6.

    For the stable distribution (trixie), these problems have been fixed in     version 5.0.2+git20231211.1364ae4-9+deb13u6.

    We recommend that you upgrade your lxd packages.

    For the detailed security status of lxd please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/lxd

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6244 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6244-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     May 02, 2026                          https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : incus     CVE ID         : CVE-2026-40195 CVE-2026-40197 CVE-2026-40243 CVE-2026-40251                      CVE-2026-41647 CVE-2026-41648 CVE-2026-41684 CVE-2026-41685

    Multiple security issues were discovered in Incus, a system container     and virtual machine manager, which could result in denial of service,

    For the stable distribution (trixie), these problems have been fixed in     version 6.0.4-2+deb13u7.

    We recommend that you upgrade your incus packages.

    For the detailed security status of incus please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/incus

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Incus is a system container and virtual machine manager. Prior to version 7.0.0, backup.GetInfo() trusts     the inline backup/index.yaml config when present and only falls back to parsing the legacy     backup/container/backup.yaml file if result.Config == nil. As a result, an archive can carry a valid     inline config that passes the initial import preflight while also carrying a malformed legacy     backup/container/backup.yaml file that is reparsed later from the restored file system.
    ParseConfigYamlFile() accepts YAML documents with no container section, and multiple downstream consumers     then dereference. Container without checking for nil. Confirmed examples in the instance restore and     import flow include backup.UpdateInstanceConfig() and internalImportFromBackup(). An authenticated user     with permission to import instance backups may be able to crash the Incus daemon with a crafted backup     archive whose inline backup/index.yaml is valid but whose extracted legacy backup.yaml omits container.
    The crash occurs in the restore path after archive extraction has begun. This issue has been patched in     version 7.0.0. (CVE-2026-41684)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
339353	GLSA-202608-23 : Incus: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	Local	high
312104	Debian dsa-6247 : golang-github-canonical-lxd-dev - security update	Nessus	Debian Local Security Checks	Local	high
311800	Debian dsa-6244 : golang-github-lxc-incus-dev - security update	Nessus	Debian Local Security Checks	Local	high
311647	Linux Distros Unpatched Vulnerability : CVE-2026-41684	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-41684

medium

Tenable Plugins

high

high

high

medium