The Incus advisory says a client reaching its HTTPS listener can be treated as a trusted certificate holder without possessing that certificate's private key. The flaw can grant cluster-level access.The vendor published its advisory on 29 October 2026, and the CVE record was published on 18 November 2026. The later CVE date does not mark a later patch. Incus 7.6.0 is the vendor's fixed threshold.
What it allows
How Does CVE-2026-130778 Bypass Incus Authentication?
The HTTPS listener requests client certificates but does not verify their chains. According to the Incus advisory, the handshake proves possession of only the first certificate's private key. Incus then compares every presented certificate with its trust store, even though later certificates are client controlled.
That mismatch can let a remote client assume the identity of a trusted client, metrics or server certificate. The vendor says a reachable server certificate is presented during a normal TLS handshake, so prior Incus access is not required for this route. A forged trusted identity can bypass authorization and reach internal cluster functions.
The advisory also describes changes to trust store entries and affected host-to-virtual-machine agent authentication. Unverified chains reach authorization scriptlets as well, potentially influencing their decisions. Token and OIDC clients are included in that scriptlet concern, even when they do not authenticate through mutual TLS.
Use Vulnerability Intelligence to put reachable Incus instances and the fixed release in one review queue. The LXD certificate chain bypass profile covers a separately identified product and CVE.
What Does the Evidence Say About Exploitation?
The CISA KEV catalog version 2026.11.17 did not list CVE-2026-130778. That dated catalog status is not an assessment of any individual Incus deployment. The advisory and CVE record describe impact, but neither provides an incident count.
Who is affected
Which Incus Installations Need Review?
The Incus advisory lists versions before 7.6.0 as affected and 7.6.0 or later as patched. It says the behavior dates to the initial release. The relevant exposure is network reachability to the Incus HTTPS listener, rather than membership in a cluster alone.
Inventory running Incus versions and identify which hosts can reach each HTTPS listener. Treat listeners reachable beyond trusted hosts as the first upgrade candidates. For clustered installations, include every member in the version check and record the running version after the change.
The vendor says access to the HTTPS listener can be restricted to trusted hosts as a temporary measure. It does not offer a configuration-based workaround. Keep that network restriction until the upgrade is complete and verified through the patch management process.
Timeline
-
2026-10-29
The Incus project published GHSA-xg75-xf37-cph9 and named 7.6.0 as the patched version.
-
2026-11-18
The CVE Program published CVE-2026-130778, linking the Incus advisory and recording both CVSS scores.
What to do
-
Inventory Incus listeners and versions
Record each running Incus version and the hosts able to reach its HTTPS listener. Include every cluster member and host-to-virtual-machine agent connection in the review.
-
Restrict listener access during remediation
Limit network access to trusted hosts while upgrading. The Incus advisory says there is no configuration-based workaround.
-
Upgrade Incus to 7.6.0 or later
Upgrade affected installations using the vendor's supported release path. Prioritize externally reachable listeners, then complete every affected cluster member.
-
Verify the running release and review activity
Confirm each running instance reports 7.6.0 or later after the upgrade. Review trust store changes, certificate management and unusual cluster access; these checks are defensive recommendations, not evidence of exploitation.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-130778 in Brandefense Atlas
The Atlas record of CVE-2026-130778: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-130778 require an Incus account?
The Incus advisory says a client that can reach the HTTPS listener may impersonate a trusted certificate without prior Incus access. Network reachability is the key exposure condition.
Which Incus version fixes CVE-2026-130778?
The vendor lists versions before 7.6.0 as affected and 7.6.0 or later as patched. Verify the version actually running on every instance.
Can an Incus setting replace the upgrade?
No configuration-based workaround is listed by the vendor. Restrict HTTPS listener access to trusted hosts while upgrading to Incus 7.6.0 or later.
What is the relationship between the October advisory and November CVE?
The Incus advisory appeared on 29 October 2026. The same issue received CVE-2026-130778 on 18 November 2026; the later date is the CVE publication date.
Sources
- Authentication and Authorization Bypass Through Unverified Client Certificate ChainsIncus project
- CVE-2026-130778 RecordVulnCheck via CVE Program
- CISA Known Exploited Vulnerabilities CatalogCISA