Skip to main content
Menu
CVEs

CVE

Incus token exposure in operation event stream

Affects Incus before 7.6.0, including restricted clients trusted for the default project and any authenticated client that knows an operation UUID. Fixed in 7.6.0.

CVE-2026-130783Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 7.6.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Attacker must be a restricted client trusted for the default project, or any authenticated client that knows an operation UUID.

Summary

Incus before 7.6.0 exposes certificate and cluster join token secrets through the default project event stream and skips authorization when cancelling operations without associated permissions. Restricted clients can subscribe to operation events to capture certificate tokens and enroll unrestricted certificates, gaining full server access, or cancel token operations by UUID.

Who should check

Teams running Incus (incusd) before v7.6.0 that issue restricted certificates for the default project, including Go services depending on github.com/lxc/incus/v7/cmd/incusd

“Affected versions < v7.6.0”

github.com

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Attacker must be a restricted client trusted for the default project, or any authenticated client that knows an operation UUID.
  • Upgrade to a fixed version: 7.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130783 (Incus before 7.6.0 Token Exposure and Missing Authorization via Operation Events), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130783 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- Attacker must be a restricted client trusted for the default project, or any authenticated client that knows an operation UUID. (source: https://github.com/lxc/incus/security/advisories/GHSA-cwg9-8mc4-hf7j)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130783 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130783 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-cwg9-8mc4-hf7j
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130783
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130783"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-cwg9-8mc4-hf7j
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130783
RecordNVD · CVE-2026-130783

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130783

Is CVE-2026-130783 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Operation events can expose a certificate or cluster join token, which a client could use to enroll an unrestricted certificate and gain full server access. Permission-less operations can also be cancelled by UUID.Source: github.com

Which versions are affected by CVE-2026-130783?

github.com/lxc/incus/v7/cmd/incusd (Go): before 7.6.0.Source: cve.now feed data

Am I affected, and how do I check?

Incus versions before 7.6.0 are in range. The exposure applies to restricted clients trusted for the default project, or to any authenticated client that knows an operation UUID. To check an installed version, run incus version.Source: github.com

How do I fix CVE-2026-130783?

Upgrade Incus to 7.6.0 or later, which is the version that fixes this vulnerability.Source: github.com

More CVEs