On this page (7 sections)
A critical authentication bypass has been published for Incus, the container and virtual machine manager. According to the NVD record for CVE-2026-130778, versions before 7.6.0 let a remote attacker authenticate as any trusted certificate by appending that certificate's public certificate to the TLS client chain they present.
If you run Incus, especially in a cluster, and its API can be reached over a network, treat this as urgent. The record lists a CVSS score of 10. This article sticks to what the public record says and marks the gaps clearly.
What happened
NVD published the record on 2026-11-18. It describes an authentication bypass in Incus: a remote attacker can authenticate as any trusted certificate by appending that certificate's public certificate to the TLS client chain they present. The record points to a GitHub advisory, GHSA-xg75-xf37-cph9, as a reference. The research does not include the text of that advisory, so we have not reviewed what it says.
Only one independent publisher covers this story so far, and the NVD text is the only content we have. There is no confirmation of exploitation, no proof of concept and no detailed vendor write-up in the material available, so several questions below are marked as unknown.
Technical details in plain terms
The weakness class is CWE-287, improper authentication. In general terms, this means the server can be convinced that a caller is someone they are not. Per NVD, the trick here involves the certificate chain a client presents during the TLS connection: adding a trusted certificate's public certificate to that chain is enough to be treated as that certificate.
The NVD text does not explain the root cause. It is a reasonable guess that the server does not properly tie the presented identity to the client's own credentials, but that is our interpretation, not something the record states.
The record says an attacker can append the server's certificate or a cluster member's certificate. The listed consequences are:
- Cluster-level access.
- Bypassing authorization.
- Modifying trust store entries.
- Influencing scriptlet-based authorization decisions.
Who is affected
Per the record, Incus versions before 7.6.0 are affected, and the attacker is described as remote. Beyond that, the research gives no deployment details, so the points below are practical guidance rather than confirmed facts:
- Hosts where the Incus API is reachable over a network should be treated as the highest priority, since the record describes remote attackers.
- Clusters are called out specifically: the record says a cluster member's certificate can be used to gain cluster-level access.
- Hosts where the API is not network-reachable may have less exposure, but the research does not confirm this. Update them anyway.
- Hosting providers and agencies running customer workloads on Incus should include those hosts in their review, since the record describes access at the cluster and authorization level.
How to check your exposure
First find out which version you run. This command prints the Incus client and server versions on the host and changes nothing. Look for a server version lower than 7.6.0.
incus versionNext, check whether anything is listening on the network. This standard Linux command lists listening TCP sockets with the owning process, so you can see whether Incus is bound to a network address. Run it as root to see process names, and look for Incus entries.
ss -tlnpThen review the trust store for certificates you do not recognize. This read-only listing shows the trusted client certificates, so compare it against your own records.
incus config trust listWhat to do now
- Inventory every Incus host and cluster member and record the version of each.
- Upgrade to Incus 7.6.0 or later through your distribution's or the project's normal update channel. The fixed version is inferred from the affected range, so confirm it in the vendor advisory.
- Read the GitHub advisory referenced by NVD for fix details and any guidance on upgrading clusters, since we have not reviewed it.
- Until you can upgrade, limit network access to the Incus API with a firewall or private management network so only known admin hosts can connect. This reduces exposure but is not described as a fix in the research.
- Review the trust store and investigate any certificate you cannot account for.
- Check cluster membership and recent configuration changes for anything unexpected.
- Review Incus and host logs for client connections from unfamiliar addresses.
- If you find signs of unauthorized access, treat the host as compromised and follow a recovery process, including rotating certificates and credentials.
Detection and monitoring
No exploitation details are public in the research, so there is no known indicator to search for. Focus on changes that a successful bypass could plausibly cause, based on the consequences NVD lists: new or altered trust store entries, unexpected cluster configuration changes, and API connections from addresses outside your admin range.
Keep logs from the Incus host and any firewall or proxy in front of it, and ship them to a place an attacker on the host cannot easily edit. If your management endpoints sit behind a public hostname, certificate and DNS monitoring can alert you when certificates or records change unexpectedly, and the free SSL checker lets you inspect what a public endpoint presents. Neither replaces patching, and neither is specific to this flaw.
For wider hygiene, see our guide to small business website security, and if you suspect a compromise, what to do when a website is hacked.
What is still unknown
- Whether the flaw is being exploited in the wild. The research does not say, and no source marks it as exploited.
- The CVSS vector and which organization assigned the score of 10.
- The root cause and the exact fix, which should be read in the vendor advisory.
- Whether any configuration or workaround prevents the issue short of upgrading.
- Which deployments are reachable by default.
Treat the NVD record and the project advisory as the authoritative sources and re-check them for updates.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
