CVE-2026-48751: Incus Restricted Project Bypass Leading to Arbitrary Command Execution

Vulnerability Overview

CVE-2026-48751 is a critical missing authorization vulnerability (CWE-862) in Incus, the open-source system container and virtual machine manager maintained under the LXC project. The flaw resides in the incusd daemon and allows an attacker with access to a restricted Incus project to bypass all project-level restrictions and execute arbitrary commands directly on the host system — a full container escape. With a CVSS score of 9.9, this ranks among the most severe container runtime vulnerabilities disclosed in 2026.

At its root, the daemon fails to enforce authorization checks when processing certain API requests scoped to restricted projects. A restricted project is Incus's primary tenant-isolation primitive; its bypass nullifies the security boundary that operators rely on to separate workloads and limit blast radius on shared infrastructure.

Affected Software

• Package: github.com/lxc/incus/v7/cmd/incusd
• Ecosystem: Go
• Affected versions: all releases prior to 7.2.0

No patch date has been published at the time of this writing. Operators running any Incus version below 7.2.0 should treat their installations as actively at risk.

Exploitation Status

A public proof-of-concept (PoC) is available as of the disclosure date (2026-06-26). This materially lowers the bar for exploitation — any attacker with a foothold inside a restricted Incus project, including low-privileged tenants on a shared host, can leverage the PoC to escalate to host-level code execution. Defenders should treat this as an actively weaponizable vulnerability and prioritize detection and mitigation immediately, even in the absence of confirmed in-the-wild exploitation.

Detection Coverage

Our detection engineering team has shipped query-based coverage across seven SIEM platforms for this CVE:

• Microsoft Sentinel (KQL)
• Splunk (SPL)
• Elastic (EQL)
• IBM QRadar (AQL)
• Sumo Logic
• Google Chronicle (YARA-L)
• CrowdStrike (CQL)

The detection logic centers on several observable signals that accompany exploitation of this bypass: anomalous API calls from restricted project contexts that trigger operations outside their permitted scope, unexpected process spawning from incusd lineage on the host, and privilege escalation patterns consistent with container escape — such as host filesystem access or privileged system calls originating from a containerized security context. Where endpoint telemetry is available, detections also surface unexpected child processes of incusd executing with host-level privileges.

Recommended Response

Until Incus 7.2.0 is released and deployed, consider restricting API access to incusd to trusted principals only, auditing all existing restricted project memberships, and enabling host-level process monitoring to catch escape attempts in progress.

Full Detection

The complete KQL, SPL, EQL, AQL, Sumo Logic, Chronicle YARA-L, and CrowdStrike CQL queries — along with playbook guidance and atomic test cases — are available on the CVE-2026-48751 detection page.