CVE-2026-33743: lxc incus · Unthrottled Resource Allocation
Affects lxc incusSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 6.23.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.23.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade incus and lxc/incus to 6.23.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| lxcincus | Affected
| Fixed in
|
GitHublxc/incuspkg:github/lxc/incusOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Incus to version 6.23.0 or later, where this vulnerability is fixed. Since this is an official fix, applying the update fully mitigates the issue. No other mitigations are indicated.
Description
CVE-2026-33743 is a medium severity vulnerability in the Incus system container and virtual machine manager prior to version 6.23.0. It involves allocation of resources without limits or throttling when processing specially crafted storage bucket backups. An attacker with access to the storage bucket feature can exploit this to crash the Incus daemon, causing a denial of service of the control plane API. This does not affect running workloads or existing containers and virtual machines, which continue operating normally. The issue is fixed in version 6.23.0.