CVERadar
CRITICAL · CVSS 4.0 9.4EPSS n/aThreat level 47

CVE-2026-130786: CVE-2026-130786: Incus before 7.6.0 contains a configuration injection vulnerability that allows users who …

Unknown · Incus · NVD published 2026-11-19 · posted 2026-11-18 · last modified 2026-11-19

CVE-2026-130786 at a glance

CVE-2026-130786 is a critical-severity Injection vulnerability in Incus, with a CVSS 4.0 base score of 9.4. NVD published it on 2026-11-19 and classifies the weakness as CWE-74. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 47/100.

What it is

Incus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects.

WeaknessCWE-74 definition
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: VulnCheck)
ATT&CK tacticsn/a

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources