CVE
Incus auth bypass in TLS client certificate chain validation
Incus versions before 7.6.0 are affected, specifically through the HTTPS listener, which requests client certificates without verifying them. CVSS rates it Critical (10). Fixed in 7.6.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.6.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
Summary
Incus before 7.6.0 contains an authentication bypass vulnerability that allows remote attackers to authenticate as any trusted certificate by appending its public certificate to their presented TLS client chain. Attackers can append the server's or a cluster member's certificate to gain cluster-level access, bypass authorization, modify trust store entries, and influence scriptlet-based authorization decisions.
Who should check
Teams running Incus (lxc/incus, incusd) before 7.6.0 with the HTTPS listener reachable over the network, including cluster deployments.
“Affected versions < v7.6.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach10/20Affects Go packages
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
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-130778 (Incus before 7.6.0 Authentication Bypass via Unverified Client Certificate Chains), 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-130778 (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):
- Incus versions before 7.6.0 are affected. (source: https://github.com/lxc/incus/security/advisories/GHSA-xg75-xf37-cph9)
- Client certificates are requested on the HTTPS listener but not verified, so the first certificate in the presented chain is the only one proven. (source: https://github.com/lxc/incus/security/advisories/GHSA-xg75-xf37-cph9)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130778 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130778 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-xg75-xf37-cph9
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-130778
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-130778"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
fixed in 7.6.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · lxc/incus · Advisory GHSA-xg75-xf37-cph9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130778 |
| Record | NVD · CVE-2026-130778 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130778
Is CVE-2026-130778 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?
The HTTPS listener requests client certificates but does not verify them, so only the first certificate in a presented chain is proven. An attacker who can reach the listener can authenticate as any trusted client, metrics or server certificate holder, including a cluster member, which bypasses authorization.Source: github.com
Which versions are affected by CVE-2026-130778?
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 affected. To check an installed version, run incus --version, and check whether the HTTPS listener is enabled by looking at the core.https_address setting.Source: github.com
How do I fix CVE-2026-130778?
Upgrade Incus to version 7.6.0 or later, which is the fixed version named in the affected range.Source: github.com