Vulnerability in incus (DEBIAN-CVE-2026-62940)

Summary

Vulnerability in incus (DEBIAN-CVE-2026-62940). Successful exploitation can lead to full system takeover. Exploitable via security.privileged. Mitigation: upgrade to 6.0.4-2+deb13u9 or later.

Original description

The description as published by the source.

Incus is a system container and virtual machine manager. Prior to version 7.3.0, when migrating an instance to another cluster member, user-supplied configuration overrides (including security-critical keys like security.privileged and raw.lxc) are applied without any project restriction enforcement, allowing a restricted project user to escalate to a privileged container and escape to the host. Version 7.3.0 patches the issue.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-62940 has been found in incus.
Attackers can target a specific entry point like security.privileged over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade incus to 6.0.4-2+deb13u9 or later.
If unsure, ask your IT team or search "incus DEBIAN-CVE-2026-62940" on the vendor's site.

DEBIAN-CVE-2026-62940 (incus)
Attack vector: remote (network-reachable) / no user interaction
Attack surface: security.privileged / raw.lxc
Patched: 6.0.4-2+deb13u9 — apply immediately
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.

❓ What is the problem

A vulnerability (unclassified) exists in incus. Attackers reach the vulnerable code path via security.privileged.

📍 Affected scope

Check the vendor advisory for the affected versions of incus. Attack surface: security.privileged / raw.lxc.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.0.4-2+deb13u9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
grep -r 'incus' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で incus を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade incus to 6.0.4-2+deb13u9
```
ステージング環境で 6.0.4-2+deb13u9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 incus

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.0.4-2+deb13u9"}]}]

Debian:14 incus

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.1-2"}]}]

References

advisory security-tracker.debian.org