Skip to main content
VulnerabilityPublished

CVE-2026-63125: lxc incus · Link Following

Affects lxc incusSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 7.3.0 as a priority.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 7.3.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade incus and lxc/incus to 7.3.0.

Affected software

ProductAffectedFixed in
lxcincusAffected
  • <7.3.0
Fixed in
  • 7.3.0
GitHublxc/incuspkg:github/lxc/incusOther threatsAffected
  • <7.3.0
Fixed in
  • 7.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Incus to version 7.3.0 or later, where this vulnerability is patched. No other official remediation or temporary fixes are indicated. Patch status is not explicitly confirmed in the vendor advisory, but the description states version 7.3.0 fixes the issue.

Description

Incus is a system container and virtual machine manager. Prior to version 7.3.0, an unprivileged, project-confined Incus user (a non-admin TLS/RBAC identity with `can_create_images` and `can_create_instances`) can execute arbitrary code as root on the host. A crafted image ships `backup.yaml` as a symlink to a host file. When the root daemon writes the instance's backup file, it follows the symlink. Version 7.3.0 patches the issue.

References

Community reviews

Loading reviews…