GPU VulnDB

Database/Container, Kubernetes & orchestration

Incus: a container can pose as another container on the /dev/incus guest API via a forged cgroup name

CVSS 8.4CVE-2026-130785Container, Kubernetes & orchestrationcurated

Impact

The /dev/incus guest API works out which container is calling from the caller's cgroup name. A process in one container can create a cgroup whose name contains a forged lxc.monitor. component and be treated as a different container. It can then read that container's user.* and cloud-init.* configuration and its devices, subscribe to its events, mark it ready, and export images across projects. cloud-init and user config often hold secrets or bootstrap credentials, so on a multi-tenant host this leaks one tenant's data to another and breaks project isolation.

Who can reach it

A process inside any container on an affected Incus 7.3.0-7.6.0 host that can reach /dev/incus and create a cgroup. No Incus API credentials are needed beyond running inside a container (CVSS PR:L).

What to do

Upgrade Incus to 7.6.0 or later and restart the Incus daemon. Running containers do not need a restart for the fix. Rotate any secrets kept in user.* or cloud-init.* config on hosts where untrusted tenants ran containers on an affected version.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.