CVE-2026-48749 Google Chronicle · YARA-L

Detect CVE-2026-48749: Incus Arbitrary File Read/Write via rootfs Symlink in Malicious Image in Google Chronicle

Detects exploitation of CVE-2026-48749, a critical vulnerability in Incus (github.com/lxc/incus/v7/cmd/incusd) versions prior to 7.2.0. Attackers can craft a malicious container image with symlinks in the rootfs/ directory that resolve to host filesystem paths, enabling arbitrary file read and write on the underlying host. This constitutes a container escape primitive and may lead to full host compromise. CVSS 9.9 with public PoC available.

MITRE ATT&CK

Tactic
Initial Access Persistence Privilege Escalation Defense Evasion

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_48749_incus_rootfs_symlink_escape {
  meta:
    author = "df00tech Detection Platform"
    description = "Detects CVE-2026-48749: Incus arbitrary file read/write via rootfs symlink in malicious image"
    severity = "CRITICAL"
    reference = "https://github.com/lxc/incus/security/advisories/GHSA-2q3f-q5pq-g8wv"
    cve = "CVE-2026-48749"

  events:
    $e1.metadata.event_type = "FILE_CREATION"
    $e1.principal.process.file.full_path = /incusd|incus/
    $e1.target.file.full_path = /\/var\/lib\/incus\/.*\/rootfs\//
    $e1.principal.hostname = $host

    $e2.metadata.event_type = "FILE_OPEN"
    $e2.principal.process.file.full_path = /incusd|incus/
    $e2.target.file.full_path = /\/etc\/passwd|\/etc\/shadow|\/root\/\.ssh|\/etc\/sudoers/
    $e2.principal.hostname = $host

  match:
    $host over 15m

  condition:
    $e1 and $e2
}
critical severity high confidence

Chronicle YARA-L rule correlating Incus rootfs file creation events with subsequent sensitive host file access by the incusd process within a 15-minute window.

Data Sources

Chronicle UDM - File EventsChronicle UDM - Process Events

Required Tables

udm_events

False Positives & Tuning

  • Container image build pipelines that create rootfs entries and access host configuration in sequence
  • Incus daemon initialization that reads host system files during startup after rootfs preparation
  • Authorized penetration testing activities targeting Incus environments with explicit sign-off
  • Cluster management operations synchronizing rootfs state with host configuration files

Other platforms for CVE-2026-48749


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Create malicious Incus image with rootfs symlink targeting /etc/passwd

    Expected signal: auditd syscall events for symlink() within /var/lib/incus/*/rootfs/; file open events on host /etc/passwd initiated by incusd process; DeviceFileEvents showing incusd accessing /etc/passwd outside container namespace

  2. Test 2Exploit rootfs symlink for host SSH authorized_keys write

    Expected signal: File write event on host /root/.ssh/authorized_keys attributed to incusd or container init process; auditd records showing write() syscall to /root/.ssh/authorized_keys from incusd context; FIM alert on /root/.ssh/authorized_keys modification

  3. Test 3Read host /etc/shadow via rootfs symlink for credential harvesting

    Expected signal: File read event on host /etc/shadow initiated by incusd process context; auditd openat() syscall on /etc/shadow attributed to container namespace but resolved to host inode; audit log entry for privileged file access outside expected paths

Unlock Pro Content

Get the full detection package for CVE-2026-48749 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections