Vulnerability in Incus (CVE-2026-63125)
Summary
Vulnerability in Incus (CVE-2026-63125). Successful exploitation can lead to full system takeover. Exploitable via can_create_images.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63125 has been found in Incus.
Attackers can target a specific entry point like can_create_images over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Incus CVE-2026-63125" on the vendor's site.
CVE-2026-63125 (Incus) — CWE-59 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: can_create_images / can_create_instances / backup.yaml
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-59) exists in Incus. Attackers reach the vulnerable code path via can_create_images.
Check the vendor advisory for the affected versions of Incus. Attack surface: can_create_images / can_create_instances / backup.yaml.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Incus' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Incus' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Incusを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-63125 incus Fixed in: 6.0.4-2+deb13u9
- Ubuntu UBUNTU-CVE-2026-63125 incus
References
- web github.com