#Incus
agents can't bypass your guardrails if you have no guardrails
November 15, 2026 at 6:37 PM
opsmaru_incus 0.1.0 [new]

Portable native Incus client, embeddable native gateway and shared Incus operations

Licenses: Apache-2.0
November 12, 2026 at 9:15 AM
incus
November 7, 2026 at 10:21 PM
Au #cdl2026, on ne fait pas qu'écouter : ateliers de 2h sur Guix & NixOS, Bareos, Silex, Incus, Vim, un assistant IA en local et même un escape game de tracing Linux. Apportez votre portable ! capitoledulibre.org/programme/
November 10, 2026 at 11:02 AM
Ops, SRE, DevOps : Kubernetes Gateway API, OpenTofu, Incus, OpenStack-Helm, Garage et « jq like a boss ». Votre parcours infra au #cdl2026 est prêt. capitoledulibre.org/programme/
November 12, 2026 at 8:25 AM
Critical infrastructure alert: LXD, MicroCloud and Incus certificate trust bypass

SecPoint Penetrator helps teams review network exposure.

Free scan: www.secpoint.com/free-vulnera...
Partners: www.secpoint.com/partner-sign...

#CyberSecurity #LXD #Incus #MicroCloud #SecPoint
November 9, 2026 at 7:58 AM
I use OpenCode and run it exclusively in disposable VMs with only the creds/files that are relevant to what it needs to do injected. Then I let it have full access to everything within the VMs.

I use Incus to manage it, and I vibe-coded Incus wrapper scripts within a VM (developed in nested virt).
November 11, 2026 at 6:15 PM
I would start here: community-scripts.org/scripts?q=ne...
They have both VM and Docker options. If you want to have things setup but not have to go through each and every step, the Community Scripts are excellent.
All scripts | Community Scripts
Browse all community scripts for Proxmox VE and Incus.
community-scripts.org
November 14, 2026 at 4:59 PM
Incus is one tool for Linux system containers and VMs. A system container is a full distro (Ubuntu, Debian, Fedora, Arch and more) on the host kernel, with very low overhead. Need Windows or your own kernel? Same commands, a QEMU VM. CPU and memory limits via profiles.

linuxcontainers.org/incus
November 10, 2026 at 7:01 AM
Word of the Hour: Mastax - The pharynx of a rotifer. It usually contains four horny pieces. The two central ones form the incus against which the mallei or lateral ones work so as to crush the food. #WordOfTheHour #WordOfTheDay
November 12, 2026 at 1:00 AM
depending on what I'm doing with them incus or microvm.nix. microvm.nix would really only be for something like ephemeral CI runners tho
November 7, 2026 at 10:32 PM
incus (⭐️ 6609)

Powerful system container and virtual machine manager

#go
November 8, 2026 at 9:10 AM
Birger Schacht: Using incus for throw away VMs
For some time now I’ve been looking for a way of keeping projects I’m working on in a separate VM without much setup. There are numerous solutions to do this kind of thing using namespaces (various container technologies, firejail, flatpak, bubblewrap, …) but I wanted something that uses real virtualization. I recently stumbled upon incus and it seemed like it could be a solution to my problem. Incus is a manager for both containers and virtual machines. It is possible to create VM images that can be used as templates, meaning that other machines can then be based on them on creation. Virtual machines can be configured using “profiles”. For my use case, I have created a profile that defines how my template image should look like. In this profile I use cloud-init to configure the template machine on startup: config: cloud-init.user-data: | #cloud-config apt: conf: | APT { Install-Recommends 0; } package_update: true package_upgrade: true package_reboot_if_required: true packages: - file - man-db - bat - eza - git - git-delta - neovim - zsh - tmux - curl - ncurses-term - hx - nix-bin - nix-setup-systemd - rustup - npm - podman users: - name: user lock_passwd: false # mkpasswd 'incus password' hashed_passwd: $y$j9T$p9XBP4Ox3SBUnyu.sqv5m1$f1rxcPJyVs05w./dZvIzu6.4dVWBvzu99nMBZRNlamD groups: sudo, nix-users shell: /usr/bin/zsh uid: 1000 write_files: - path: /home/user/.config/nix/nix.conf content: | experimental-features = nix-command flakes permissions: 0600 - path: /home/user/.zshrc.local content: | export PATH="$PATH:$HOME/.nix-profile/bin" permissions: 0600 runcmd: - [curl, -sSfL, -o, /home/user/.tmux.conf, https://grml.org/console/tmux.conf] - [curl, -sSfL, -o, /home/user/.vimrc, https://grml.org/console/vimrc] - [curl, -sSfL, -o, /home/user/.zshrc, https://grml.org/console/zshrc] - [chown, -R, user:user, /home/user/] description: Base template for dev VMs ... and I use a script to regenerate the template image when I want to adapt the config: #!/bin/sh #set -e set -x NAME=dev-vm-template # adapt the profile before rebuilding the template image incus profile edit cloud-dev-template incus delete --force ${NAME} || true incus create images:debian/13/cloud --vm --quiet --profile default --profile cloud-dev-template ${NAME} incus start ${NAME} incus wait ${NAME} agent incus exec ${NAME} -- cloud-init status --wait || true incus stop ${NAME} incus publish --alias cloud-dev-template --reuse ${NAME} This script uses the `debian/13/cloud` image together with my `cloud-dev-template` profile to set up a machine, configure it using `cloud-init` and store the result as an image called `cloud-dev-template`. ## inker To use this setup, I created a small python tool called inker that talks to the incus REST API. Using `inker create` creates a new VM based on my template. Using `inker attach` attaches the current working directory to a VM as a readonly mount. It is possible to combine those commands like `inker create | inker attach` to do those two steps in one command. `inker login` logs into the VM that has the current directory attached. This way I can create VMs that are connected to directories on my filesystem. I am currently playing around with this setup, but I think this could help me to have a throwaway development machine, similar to dev containers. I’m not sure yet how happy I am with `incus`, though. I was also looking at systemd-vmspawn, but there are still some features missing that I would need. But I might rewrite `inker` at some point to use a different backend.
bisco.org
November 8, 2026 at 4:54 PM
GHSA-47W9-6R3F-938G: GHSA-47w9-6r3f-938g: Authorization Bypass and Host Root Command Execution in Canonical LXD and Incus
# GHSA-47w9-6r3f-938g: Authorization Bypass and Host Root Command Execution in Canonical LXD and Incus > **Vulnerability ID:** GHSA-47W9-6R3F-938G > **CVSS Score:** 9.9 > **Published:** 2026-11-06 A missing authorization and configuration validation vulnerability in Canonical LXD and LXC Incus allows authenticated users within restricted projects to bypass project security boundaries. By smuggling prohibited low-level configuration directives (such as raw.lxc or raw.qemu) inside instance snapshots or backup archives, an attacker can restore these configurations within a restricted project and execute arbitrary commands with root privileges on the underlying host operating system. ## TL;DR Authenticated users in restricted LXD or Incus projects can bypass security restrictions by restoring instance snapshots or importing backups containing prohibited low-level hypervisor hooks (e.g., raw.lxc), leading to arbitrary command execution as root on the host OS. ### ⚠️ Exploit Status: POC ## Technical Details * **Vulnerability ID** : GHSA-47w9-6r3f-938g / CVE-2026-48751 * **Weakness Class** : CWE-862: Missing Authorization * **Attack Vector** : Network (REST API) * **CVSS v3.1 Score** : 9.9 Critical (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) * **EPSS Score** : 0.68% (52.67th Percentile) * **Security Impact** : Container Escape / Host Root Command Execution * **Exploit Status** : Public Proof-of-Concept Available * **CISA KEV Status** : Not Listed ## Affected Systems * Canonical LXD * LXC Incus * **LXD (LTS 4.0 / 5.0 series)** : >= 4.12.0, < 5.0.7 (Fixed in: `5.0.7`) * **LXD (LTS 5.21 series)** : >= 5.1.0, < 5.21.5 (Fixed in: `5.21.5`) * **LXD (Feature series)** : >= 6.0.0, < 6.9.0 (Fixed in: `6.9.0`) * **Incus** : < 7.2.0 (Fixed in: `7.2.0`) ## Code Analysis ### Commit: 5aac658 Validate instance snapshots against project restrictions when importing from backup in lxd/instances_post.go diff --git a/lxd/instances_post.go b/lxd/instances_post.go --- a/lxd/instances_post.go +++ b/lxd/instances_post.go @@ -932,6 +902,56 @@ func createFromBackup(s *state.State, r *http.Request, projectName string, data + // Check restrictions/limits if defined on project. + if restrictions != nil { + err = limits.AllowInstanceCreation(s.GlobalConfig, *restrictions, req) + if err != nil { + return response.SmartError(err) + } + + for i, snapshot := range bInfo.Config.Snapshots { + if snapshot == nil { + return response.SmartError(fmt.Errorf("Nil instance snapshot definition found at index %d", i)) + } + + snapshotReq := api.InstancesPost{ + InstancePut: api.InstancePut{ + Architecture: snapshot.Architecture, + Config: snapshot.Config, + Devices: snapshot.Devices, + Ephemeral: snapshot.Ephemeral, + Profiles: snapshot.Profiles, + Stateful: snapshot.Stateful, + }, + Name: bInfo.Name + "/" + snapshot.Name, + Source: api.InstanceSource{}, + Type: api.InstanceType(bInfo.Config.Instance.Type), + } + + err = limits.AllowInstanceCreation(s.GlobalConfig, *restrictions, snapshotReq) + if err != nil { + return response.SmartError(err) + } + } + } ### Commit: a52e5d0 Validate snapshot config against project limits and restrictions during snapshot restore in lxd/instance_put.go (master) diff --git a/lxd/instance_put.go b/lxd/instance_put.go --- a/lxd/instance_put.go +++ b/lxd/instance_put.go @@ -235,6 +235,32 @@ func instanceSnapRestore(s *state.State, projectName string, name string, snap s } } + // Build the instance config that restoring the snapshot would apply, so it can be + // validated against the project's restrictions and limits below. + snapProfileNames := make([]string, 0, len(source.Profiles())) + for _, profile := range source.Profiles() { + snapProfileNames = append(snapProfileNames, profile.Name) + } + + snapConfig := api.InstancePut{ + Config: source.LocalConfig(), + Devices: source.LocalDevices().CloneNative(), + Profiles: snapProfileNames, + } + + err = s.DB.Cluster.Transaction(s.ShutdownCtx, func(ctx context.Context, tx *db.ClusterTx) error { + return limits.AllowInstanceUpdate(ctx, s.GlobalConfig, tx, projectName, name, snapConfig, inst.LocalConfig()) + }) + if err != nil { + return err + } + // Generate a new `volatile.uuid.generation` to differentiate this instance restored from a snapshot from the original instance. source.LocalConfig()["volatile.uuid.generation"] = uuid.New().String() ### Commit: 6b93b2a Backport of snapshot restore project restriction validation to LXD 5.0 branch ### Commit: cfd9f66 Backport of snapshot restore project restriction validation to LXD 5.21 branch ## Exploit Details * GitHub Security Advisory: Official advisory containing the proof-of-concept CLI commands to bypass project restrictions via snapshot restoration. * GitHub Security Advisory (Incus): Upstream Incus security advisory detailing the reproduction steps using incus CLI. ## Mitigation Strategies * Upgrade Canonical LXD or LXC Incus to a patched version that enforces project restriction checks during snapshot restoration and backup ingestion. * Audit all existing instances and snapshots in restricted projects for unauthorized low-level configuration keys such as raw.lxc and raw.qemu. * Restrict untrusted users from migrating instances across projects or importing custom backup tarballs until patches are applied. **Remediation Steps:** 1. For Canonical LXD 5.0 LTS environments, upgrade the snap or package to version 5.0.7 or later. 2. For Canonical LXD 5.21 LTS environments, upgrade the snap or package to version 5.21.5 or later. 3. For Canonical LXD 6.x environments, upgrade to version 6.9.0 or later. 4. For LXC Incus environments, upgrade the incus package to version 7.2.0 or later. 5. Run an API audit across all restricted projects using 'lxc query /1.0/instances?recursion=2' (or 'incus query') to identify and delete any snapshots or active configurations containing prohibited raw.* directives. ## References * GitHub Advisory GHSA-47w9-6r3f-938g (Canonical LXD) * GitHub Advisory GHSA-48q5-w887-33wv (LXC Incus) * National Vulnerability Database (NVD) - CVE-2026-48751 * Official CVE.org Record - CVE-2026-48751 * Canonical LXD Fix Commit: Backup Snapshot Validation (5aac658c) * Canonical LXD Fix Commit: Snapshot Restore Validation Master (a52e5d06) * Canonical LXD Fix Commit: Snapshot Restore Validation 5.0 (6b93b2a0) * Canonical LXD Fix Commit: Snapshot Restore Validation 5.21 (cfd9f66f) * Canonical LXD Release 5.0.7 * Canonical LXD Release 5.21.5 _Read the full report for GHSA-47W9-6R3F-938G on our website for more details including interactive diagrams and full exploit analysis._
dev.to
November 6, 2026 at 8:36 PM
Another great option is linuxcontainers.org/incus/ which serves a different purpose than Docker, Docker-Compose but still significantly easier to operate.
Linux Containers - Incus - Introduction
The umbrella project behind Incus, LXC, LXCFS, Distrobuilder and more.
linuxcontainers.org
November 5, 2026 at 4:43 AM
🚨 EUVD-2026-63983
📊 9.9/10
🏢 Canonical

📝 Incus is a system container and virtual machine manager. Prior to version 7.2.0, an arbitrary file write exists in the Incus client when a malicious ima...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-63983

#cybersecurity #infosec #cve #euvd
November 6, 2026 at 1:01 AM
salutations today I will be reviewing The Scream by Edvard Munch, Needs a lot more frontal lobe protector. I feel the piece feels bare bones, could use some animal skulls to spice it up. I would give this piece a 3/10. Perhaps the addition of a good Incus could raise it’s score. adios friends
November 8, 2026 at 12:56 AM
incusに脆弱性修正がきた。 LXDの対応とおなじやつ?

[SECURITY] [DSA 6604-1] incus security update
lists.debian.org/debian-secur...
[SECURITY] [DSA 6604-1] incus security update
lists.debian.org
November 3, 2026 at 6:47 AM
UW–Madison Assistant Professor and CSU alum Gabrielle "Bee" Leung presented at the NASA mission INCUS team meeting this week. A hundred researchers, engineers and students joined the meeting to discuss the state of the mission, ongoing research and work to come.
November 6, 2026 at 2:28 PM
incus (⭐️ 6585)

Powerful system container and virtual machine manager

#go
November 4, 2026 at 6:26 PM
🚨 EUVD-2026-63978
📊 9.9/10
🏢 lxc

📝 Incus is a system container and virtual machine manager. Prior to version 7.2.0, instance snapshots ignore the `restricted.containers.lowlevel=block` setting;...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-63978

#cybersecurity #infosec #cve #euvd
November 5, 2026 at 11:02 PM
🚨 EUVD-2026-63982
📊 9.9/10
🏢 lxc

📝 Incus is a system container and virtual machine manager. Prior to version 7.1.0, improper validation of user-provided backup compression algorithm leads to ar...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-63982

#cybersecurity #infosec #cve #euvd
November 6, 2026 at 1:01 AM
🚨 EUVD-2026-63984
📊 7.7/10
🏢 lxc

📝 Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for custom volume copying where an attacke...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-63984

#cybersecurity #infosec #cve #euvd
November 5, 2026 at 11:03 PM