CVE-2026-48769

CVE-2026-48769 in Incus scores 9.9, but the real story is the trust-boundary inversion at its core: a compromised or malicious image server uses HTTP response headers to trigger arbitrary file writes on the Incus client, and those writes ultimately enable root command execution on the server daemon. This isn't a straightforward remote code execution — it's a client-to-server pivot that inverts how most threat models treat the client-server relationship. The client becomes the attacker's foothold to compromise the server it connects to. The mechanism almost certainly involves the Incus-Image-Hash header. The client uses this header value to determine file write targets — likely constructing paths for image manifests, cache artifacts, or configuration files that the daemon later imports and parses with elevated privileges. If the header drives file path construction without validation, that's the vulnerability: the server's metadata controls where files land on the client, and the client's write privileges are sufficient to drop executables that the server daemon will subsequently run. What makes this severe isn't just the 9.9 score — it's the blast radius. Organizations running private Incus image mirrors (common in enterprise and air-gapped deployments) face the most dangerous variant: a compromised internal image server becomes a persistent pivot point, automatically compromising every Incus client that pulls from it. The CVSS captures individual impact but can't model this cascade. A single rogue mirror turns an entire infrastructure tier into targets. The 9.9 rather than 10.0 likely reflects either path constraints on the arbitrary write (limited to specific directories like image cache) or required user interaction after the header is processed. Either way, treat the gap as a temporary boundary, not a fundamental limitation — path traversal extensions to partially-constrained writes are a documented pattern in CVE genealogies. Prioritise patching to 7.2.0 immediately. Beyond that, audit your Incus deployment: if you run custom image servers, treat them as high-value targets because their compromise has downstream leverage over every connected client. The deeper architectural question is whether similar trust-boundary collapses exist elsewhere in the codebase — where server metadata controls client file operations over an authenticated connection that was assumed to be one-directional.

Reviewed through automated stages and approved by a human before publication.