Incus has arbitrary file read+write on host via templates/ symlink in malicious image
Noroxi assessment
Priority: Monitor (action score 39/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.73% (FIRST EPSS); higher than 53.2% of all records.
- 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 (Debian:13) 6.0.4-2+deb13u8; lxd (Debian:13) 5.0.2+git20231211.1364ae4-9+deb13u7; incus (Debian:14) 7.0.0-5.
Low priority for now. Upgrade to incus (Debian:13) 6.0.4-2+deb13u8; lxd (Debian:13) 5.0.2+git20231211.1364ae4-9+deb13u7; incus (Debian:14) 7.0.0-5 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, a specially crafted image or instance backup can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution. Version 7.2.0 patches the issue.
- Published
- Aug 21, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-73
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 9.9
- 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 |
|---|---|---|---|
| Debian:12 | lxd | all versions | — |
| 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/lxc/incus | all versions | — |
| Go | github.com/lxc/incus/v6 | all versions | — |
| 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
- CVE-2026-62940Incus has a project restriction bypass via instance migration config override39Monitor
- CVE-2026-62867Incus has an argument injection in storage volume block.create_options that leads to arbitrary command execution39Monitor
- CVE-2026-48769Incus has an arbitrary file write on its client due to trusted image hash39Monitor
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 |
|---|---|---|
| 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/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.
No commit or PR link among the references.
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-487490 days apartIncus has an arbitrary file read+write on host via rootfs/ symlink in malicious image39Monitor
- CVE-2026-487500 days apartIncus has an arbitrary file write on host via `exec-output` symlink in crafted image39Monitor
- CVE-2026-487530 days apartIncus has an arbitrary file write via path traversal in S3 multipart upload39Monitor
- CVE-2026-633430 days apartArbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root39Monitor
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
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
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
- High
- Availability impact
- High
Weakness class (CWE)
CWE-73 · External Control of File Name or PathCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Leverage Alternate EncodingCAPEC-267likelihood: High · High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- URL EncodingCAPEC-72likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
- Using UTF-8 Encoding to Bypass Validation LogicCAPEC-80likelihood: High · High
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.