llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/lxc/incus/v7/cmd/incusd

GHSA-XG75-XF37-CPH9

Authentication and authorization bypass through unverified client certificate chains

Parche disponible
Descargar PNG JSON
CVSS 3.1
10.0
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónv7.6.0
Exposición20 dDesde la divulgación, 29 oct 2026, 5:17 p. m.
Detección20 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
29 oct 26
19 nov 26
29 oct 26
4 nov 26
9 nov 26
14 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-XG75-XF37-CPH9 divulgada · CVSS 10 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Summary

The HTTPS listener requests client certificates without verifying them,
so the TLS handshake only proves that the client holds the private key
of the first certificate in the chain it presents. The remaining
certificates are entirely client controlled.

The authentication and certificate ownership checks compared every
certificate in the presented chain against the trust store. A client
could therefore authenticate as any trusted certificate by appending
that certificate's public part to its own chain, without holding the
matching private key.

This has been the case since the initial release.

Impact

Any client able to reach the HTTPS listener can authenticate as any
trusted client, metrics or server certificate for which it has the
public certificate, including as a cluster member, which bypasses
authorization entirely.

Server certificates are returned by every TLS handshake, so no prior
access is needed to obtain one. Appending the server's own certificate
grants access to the database gateway, and on a cluster appending
another member's certificate grants internal cluster access. Client
certificates can be read by any trusted client through the certificates
API or obtained from any server the client connected to.

The same flaw lets a client renew or delete any trust store entry
through the self-service paths, and affects the authentication of the
agent connection between the host and virtual machines.

The unverified presented chain was also passed to the authorization
scriptlet, so a client could feed it attacker-chosen certificates to
influence scriptlet-based authorization decisions. This includes
clients not authenticated through mutual TLS, such as token or OIDC
clients, which can still present an arbitrary certificate during the
handshake.

Workarounds

Restrict network access to the HTTPS listener to trusted hosts. There
is no configuration based workaround.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
github.com/lxc/incus/v7/cmd/incusd< v7.6.0
v7.6.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Gogithub.com/lxc/incus/v7/cmd/incusd
Corregida v7.6.0 — —
Versiones corregidasv7.6.0
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/lxc/incus/security/advisories/GHSA-xg75-xf37-cph9

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.