CVE-2026-55622: Incus has a project restriction bypass in instance copy across projects
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: incus (Alpine:v3.24) 7.0.1-r0; incus (Debian:13) 6.0.4-2+deb13u8; lxd (Debian:13) 5.0.2+git20231211.1364ae4-9+deb13u7.
Low priority for now. Upgrade to incus (Alpine:v3.24) 7.0.1-r0; incus (Debian:13) 6.0.4-2+deb13u8; lxd (Debian:13) 5.0.2+git20231211.1364ae4-9+deb13u7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for instance copying where an attacker knowing the name of a project that they don't have access to and the name of an instance in that project can copy the instance to a new project. This issue could allow an attacker to access secrets in instances they are not authorized to access. Version 7.2.0 patches the issue.
- Published
- Aug 21, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-284
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
lxc incus
- < 7.2.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | incus | before 7.0.1-r0 | 7.0.1-r0 |
| Debian:12 | lxd | from 0 | — |
| Debian:13 | incus | before 6.0.4-2+deb13u8 | 6.0.4-2+deb13u8 |
| Debian:13 | lxd | before 5.0.2+git20231211.1364ae4-9+deb13u7 | 5.0.2+git20231211.1364ae4-9+deb13u7 |
| Debian:14 | incus | before 7.0.0-5 | 7.0.0-5 |
| Go | github.com/canonical/lxd | before 0.0.0-20260630083100-c5184be310b1 | 0.0.0-20260630083100-c5184be310b1 |
| Go | github.com/lxc/incus | from 0 | — |
| Go | github.com/lxc/incus/v6 | from 0 | — |
| Go | github.com/lxc/incus/v7 | before 7.2.0 | 7.2.0 |
| Go | github.com/lxc/incus/v7/cmd/incusd | before 7.2.0 | 7.2.0 |
| openSUSE:Tumbleweed | incus | before 7.4-1.1 | 7.4-1.1 |
Same product
lxc: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-63343Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root39Monitor
- CVE-2026-63125Incus vulnerable to root RCE via image backup.yaml symlink39Monitor
- CVE-2026-62941Incus: Cross-project instance copy bypasses target project restrictions via TOCTOU in config merge39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-48769Aug 21, 2026 · Incus has an arbitrary file write on its client due to trusted image hash39Monitor
- ← EarlierCVE-2026-55621Aug 21, 2026 · Incus has a project restriction bypass for custom volume copy across projects30Monitor
- Later →CVE-2026-62313Aug 21, 2026 · Incus: Project restriction `restricted.containers.privilege=isolated` bypassable by omitting `security.idmap.isolated`17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:incus | 7.0.1-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:incus | 6.0.4-2+deb13u8 · Debian:13 | Package registry (OSV) |
| debian:lxd | 5.0.2+git20231211.1364ae4-9+deb13u7 · Debian:13 | Package registry (OSV) |
| Go:github.com/canonical/lxd | 0.0.0-20260630083100-c5184be310b1 | Package registry (OSV) |
| Go:github.com/lxc/incus/v7 | 7.2.0 | Package registry (OSV) |
| Go:github.com/lxc/incus/v7/cmd/incusd | 7.2.0 | Package registry (OSV) |
| opensuse:incus | 7.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-11537662 days apartIncus 7.0.1 before 7.0.2 and 7.2.0 before 7.5.0 Project Restriction Bypass via Custom Volume Copy33Monitor
- CVE-2026-556210 days apartIncus has a project restriction bypass for custom volume copy across projects30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.