CVE-2026-34178 Affecting incus package, versions <6.0.4-2+deb13u6
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-INCUS-18496048
- published1 Aug 2026
- disclosed9 Apr 2026
Introduced: 9 Apr 2026
CVE-2026-34178 (opens in a new tab)How to fix?
Upgrade Echo:latest incus to version 6.0.4-2+deb13u6 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream incus package and not the incus package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the supplied tar archive but creates the instance from backup/container/backup.yaml, a separate file in the same archive that is never checked against project restrictions. An authenticated remote attacker with instance-creation permission in a restricted project can craft a backup archive where backup.yaml carries restricted settings such as security.privileged=true or raw.lxc directives, bypassing all project restriction enforcement and allowing full host compromise.