PatchSiren cyber security CVE debrief
CVE-2026-48749 lxc CVE debrief
A specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution in Incus prior to version 7.2.0. This issue requires immediate attention from system administrators and security teams managing Incus installations, especially those with exposure to untrusted image sources. The vulnerability allows for potential arbitrary command execution on the host, arbitrary file access and modification, and potential for lateral movement and privilege escalation.
- Vendor
- lxc
- Product
- incus
- CVSS
- CRITICAL 9.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-21
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-08-21
- Advisory updated
- 2026-09-18
Who should care
System administrators and security teams managing Incus installations, especially those with exposure to untrusted image sources, should assess and remediate this vulnerability. They should verify Incus version and image source integrity, and monitor Incus installations for suspicious activity.
Why it matters
CVE-2026-48749 in Incus allows arbitrary file access and possible command execution, requiring immediate attention from system administrators and security teams.
- Possible arbitrary command execution on the host
- Arbitrary file access and modification
- Potential for lateral movement and privilege escalation
- Verification of Incus version and image source integrity
Technical summary
Incus, a system container and virtual machine manager, is vulnerable to a specially crafted image that can read or create/write arbitrary files on the host, potentially leading to arbitrary command execution. The issue is fixed in version 7.2.0. This vulnerability requires immediate attention from system administrators and security teams managing Incus installations, especially those with exposure to untrusted image sources. The vulnerability allows for potential arbitrary command execution on the host, arbitrary file access and modification, and potential for lateral movement and privilege escalation.
Defensive priority
High priority to verify and remediate Incus installations, especially in environments with untrusted image sources.
Recommended defensive actions
- Verify Incus version and upgrade to 7.2.0 or later if necessary
- Restrict access to untrusted image sources
- Monitor Incus installations for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but specific exploitation instances or additional impact details are not provided. The issue is fixed in version 7.2.0. There are no known instances of exploitation, but defenders should verify Incus version and image source integrity. System administrators and security teams should assess and remediate this vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-48749 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-48749
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-48749 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-48749
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/lxc/incus/security/advisories/GHSA-2q3f-q5pq-g8wv
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.