Back to Intelligence

CVE-2026-130784: Critical CVSS 9.9 dnsmasq Vulnerability in Incus — Detection and Remediation Guide

SA
Security Arsenal Team
November 18, 2026
8 min read

A critical vulnerability has been published in the National Vulnerability Database (NVD) under CVE-2026-130784, scoring CVSS 9.9 (CRITICAL) with a network attack vector. The flaw affects dnsmasq, a widely deployed DNS forwarder and DHCP server component, but the vulnerability pathway specifically impacts Incus (a community fork of LXD, the Linux container hypervisor) in versions before 7.6.0.

This is not a typical dnsmasq parsing bug. Instead, it is an authorization bypass vulnerability in Incus that allows restricted clients to create and access default project resources. Attackers can abuse this to create bridge networks with malicious raw.dnsmasq directives, ultimately achieving remote code execution as root on the host system. Alternatively, they can manipulate inherited resources using the ?project= parameter to escalate privileges.

For defenders, this represents a severe container escape scenario: a low-privileged attacker with API access to Incus can gain full root control over the host operating system. Given Incus's popularity in cloud and virtualization environments, immediate patching and hardening are imperative.

Technical Analysis

Affected Products and Versions

  • Product: Incus (Linux container and VM manager)
  • Affected Versions: All versions before 7.6.0
  • Component: Authorization and entitlement checks in project resource handling
  • Underlying Service: dnsmasq (used for network bridge configurations)
  • Platform: Linux hosts running Incus

CVE Details

  • CVE ID: CVE-2026-130784
  • CVSS 3.1 Score: 9.9 (CRITICAL)
  • Vector: NETWORK (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
  • Weakness: CWE-862 (Missing Authorization), CWE-863 (Incorrect Authorization)

Attack Chain (Defender's Perspective)

  1. Initial Access: Attacker gains authenticated access to the Incus API (e.g., via a compromised container, misconfigured permissions, or a low-privileged user account).
  2. Authorization Bypass: The attacker sends API requests that bypass entitlement checks by manipulating the ?project= parameter or creating resources in the default project without proper validation.
  3. Malicious Resource Creation: The attacker creates a bridge network device with a raw.dnsmasq configuration option. This option allows arbitrary dnsmasq directives to be injected into the dnsmasq configuration file.
  4. Code Execution: Since dnsmasq typically runs as root (or with high privileges) to manage network interfaces, the attacker can craft directives that execute arbitrary commands as root on the host (e.g., using dhcp-script or other executable hooks).
  5. Impact: Full host compromise, persistence, lateral movement, and data exfiltration.

Exploitation Requirements

  • Network access to the Incus API (default port 8443/TCP)
  • Valid authentication credentials (even low-privileged)
  • Ability to create network devices (which should normally be restricted)
  • The host must be running an affected Incus version with dnsmasq integration

Exploitation Status

As of the publication date (2026), there is no public proof-of-concept (PoC) exploit available in the wild, and the vulnerability is not yet listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. However, given the critical score and the straightforward nature of the attack (misuse of legitimate configuration options), defenders should assume weaponization is imminent. The vulnerability was responsibly disclosed and patched in Incus 7.6.0.

Detection & Response

SIGMA Rules

The following Sigma rules detect key behaviors associated with CVE-2026-130784 exploitation. These are designed to be low-noise and high-fidelity for Incus environments.

YAML
---
title: Incus Bridge Network Creation with Raw dnsmasq Directives
id: a1b2c3d4-5e6f-7a8b-9c0d-1e2f3a4b5c6d
status: experimental
description: Detects creation of Incus bridge networks with raw.dnsmasq configuration, which may indicate exploitation of CVE-2026-130784.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-130784
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.privilege_escalation
  - attack.t1068
logsource:
  category: process_creation
  product: linux
detection:
  selection:
    CommandLine|contains:
      - 'incus network create'
      - 'incus network set'
      - 'raw.dnsmasq'
  condition: selection
falsepositives:
  - Legitimate administrative network configuration (rare)
level: high
---
title: Incus API Project Parameter Manipulation
id: b2c3d4e5-6f7a-8b9c-0d1e-2f3a4b5c6d7e
status: experimental
description: Detects suspicious Incus API calls using the ?project= parameter to access default project resources, indicative of CVE-2026-130784 authorization bypass.
references:
  - https://nvd.nist.gov/vuln/detail/CVE-2026-130784
author: Security Arsenal
date: 2026/01/15
tags:
  - attack.privilege_escalation
  - attack.t1078
logsource:
  category: webserver
  product: linux
detection:
  selection:
    cs-uri-query|contains: '?project='
    cs-method: 'POST'
    cs-uri-stem|contains:
      - '/1.0/networks'
      - '/1.0/instances'
  condition: selection
falsepositives:
  - Legitimate multi-project operations (tune to environment)
level: medium

KQL (Microsoft Sentinel / Defender)

Use this KQL query in Microsoft Sentinel to hunt for exploitation attempts via Incus API logs or process execution. This assumes Incus API logs are ingested via Syslog or CEF.

KQL — Microsoft Sentinel / Defender
// Hunt for Incus network creation with raw.dnsmasq directives
Syslog
| where TimeGenerated > ago(7d)
| where Facility == "daemon" or Facility == "user"
| where SyslogMessage has "incus" and SyslogMessage has "network"
| where SyslogMessage has "raw.dnsmasq"
| project TimeGenerated, Computer, SyslogMessage, SeverityLevel
| order by TimeGenerated desc

// Hunt for Incus process execution with suspicious project parameter
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where FileName =~ "incus"
| where ProcessCommandLine has "network create" or ProcessCommandLine has "network set"
| where ProcessCommandLine has "raw.dnsmasq" or ProcessCommandLine has "?project="
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, AccountName
| order by TimeGenerated desc

Velociraptor VQL

Deploy this VQL artifact to hunt for evidence of exploitation on Linux endpoints running Incus.

VQL — Velociraptor
-- Hunt for Incus processes with raw.dnsmasq or suspicious project parameters
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ 'incus.*network.*(create|set)'
   OR CommandLine =~ 'raw\.dnsmasq'
   OR CommandLine =~ '\?project='

Remediation Script (Bash)

Use this Bash script to verify Incus version, check for suspicious dnsmasq configurations, and apply basic hardening.

Bash / Shell
#!/bin/bash
# CVE-2026-130784 Verification and Hardening Script
# Run as root on Incus hosts

set -e

INCUS_VERSION=$(incus version | grep -i server | awk '{print $2}')
VULNERABLE=false

# Check if Incus is installed
if ! command -v incus &> /dev/null; then
    echo "[INFO] Incus is not installed on this system."
    exit 0
fi

# Version comparison (simple check for < 7.6.0)
if [[ "$(printf '%s\n' "7.6.0" "$INCUS_VERSION" | sort -V | head -n1)" != "7.6.0" ]]; then
    echo "[ALERT] Incus version $INCUS_VERSION is VULNERABLE to CVE-2026-130784."
    VULNERABLE=true
else
    echo "[OK] Incus version $INCUS_VERSION is patched."
fi

# Check for raw.dnsmasq in network configs
echo "[INFO] Checking for raw.dnsmasq directives in Incus networks..."
incus network list --format csv | while read -r network; do
    net_name=$(echo "$network" | cut -d',' -f1)
    config=$(incus network show "$net_name" 2>/dev/null | grep -i "raw.dnsmasq" || true)
    if [ -n "$config" ]; then
        echo "[WARNING] Network '$net_name' contains raw.dnsmasq directives: $config"
        VULNERABLE=true
    fi
done

# Check dnsmasq config files for suspicious entries
echo "[INFO] Checking /var/lib/incus/dnsmasq/ for suspicious configs..."
if [ -d /var/lib/incus/dnsmasq ]; then
    grep -r "dhcp-script" /var/lib/incus/dnsmasq/ 2>/dev/null || echo "[OK] No dhcp-script found."
    grep -r "^conf-file" /var/lib/incus/dnsmasq/ 2>/dev/null || echo "[OK] No external conf-file directives."
fi

# Hardening: Restrict Incus API to localhost (if not already)
echo "[INFO] Checking Incus API binding..."
if incus config get core.https_address | grep -q "0.0.0.0"; then
    echo "[WARNING] Incus API is bound to 0.0.0.0. Consider restricting to localhost or trusted networks."
fi

if [ "$VULNERABLE" = true ]; then
    echo "[ACTION REQUIRED] System is vulnerable. Upgrade Incus to 7.6.0 or later immediately."
    exit 1
else
    echo "[OK] No immediate indicators of compromise found."
    exit 0
fi

Remediation

Immediate Actions

  1. Upgrade Incus: Update to Incus 7.6.0 or later immediately. This version contains the patch for CVE-2026-130784. Use your package manager or the official Incus repository:

    • For Ubuntu/Debian: sudo apt update && sudo apt install incus
    • For RHEL/CentOS: sudo dnf update incus
    • Verify installation: incus version
  2. Restrict API Access: If the Incus API is exposed to the network, bind it to localhost or a management VLAN only. Use firewall rules (e.g., iptables or nftables) to restrict access to trusted IPs.

  3. Audit Existing Networks: Review all Incus networks for raw.dnsmasq directives. Remove any that are not explicitly required for business purposes. Use the detection script above to identify suspicious configurations.

  4. Review Project Permissions: Ensure that users and API clients have the least privilege necessary. Restrict access to the default project and use role-based access controls (RBAC) if available.

Workarounds (If Patching Is Delayed)

If immediate patching is not possible, implement the following mitigations:

  • Disable Network Creation: Restrict the ability to create or modify networks to a small group of administrators. This can be done via Incus authorization plugins or external identity providers.
  • Monitor dnsmasq Configs: Set up file integrity monitoring (FIM) on /var/lib/incus/dnsmasq/ and /etc/dnsmasq.d/ to detect unauthorized changes.
  • Isolate Incus Hosts: Place Incus hosts in a segmented network zone with strict egress filtering to limit lateral movement if compromised.

Vendor Advisory and References

CISA Deadlines

As of now, CVE-2026-130784 is not listed in CISA KEV. However, given the criticality, organizations should treat this as a 24-48 hour patch priority for internet-facing or multi-tenant Incus deployments.

Related Resources

Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.