A critical flaw in Incus before 7.6.0 lets restricted clients capture certificate and cluster join token secrets from the default project event stream, enroll unrestricted certificates and gain full server access.
What Is It
CVE-2026-130783 is a vulnerability in the Incus daemon (incusd). VulnCheck disclosed it, and NVD published it on 2026-11-18. It is classified as CWE-200, Exposure of Sensitive Information to an Unauthorized Actor. According to the NVD description, Incus before 7.6.0 has two problems:
- Secret exposure: certificate and cluster join token secrets are exposed through the default project event stream.
- Missing authorization: authorization is skipped when operations that have no associated permissions are cancelled.
A restricted client can subscribe to operation events and capture certificate tokens. It can then use them to enroll unrestricted certificates, which gives it full access to the server. Separately, a restricted client can cancel token operations by UUID.
Why It Matters
VulnCheck rates this CRITICAL:
- CVSS 3.1: 9.6 (
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) - CVSS 4.0: 9.3
The attack works over the network with low complexity. It needs only low privileges and no user interaction. Scope is changed, and confidentiality and integrity impacts are both high.
In practice, a client that was deliberately limited to restricted access can raise itself to full server control. This undermines the trust boundary that restricted certificates are supposed to enforce.
This CVE has no CISA KEV entry, so the supplied data does not confirm active exploitation. NVD lists the record as "Deferred."
What's Vulnerable
- Vendor: lxc
- Product: Incus (
pkg:golang/github.com/lxc/incus/v7/cmd/incusd) - Affected: all versions below 7.6.0 (semver)
- Unaffected: 7.6.0
Deployments that give restricted clients access to the event stream are directly exposed to the token-capture path.
Patch Status
The affected-version data marks Incus 7.6.0 as unaffected. Administrators should upgrade to 7.6.0 or later. Because there is no KEV entry, there is no CISA-mandated action or due date. The vendor advisory on GitHub has the fix details.