Live › vulnerability › CVE-2026-105765
Go to dashboardConsul versions 1.17.0 through 2.0.4 have an authorization bypass in the agent's service mesh leaf certificate API. An attacker without a valid ACL token can retrieve a cached service leaf certificate and its private key.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 18:31 UTC. All times on this page are UTC.
Teams running Consul 1.17.0 through 2.0.4 as a service mesh, including Consul Enterprise, where the agent's leaf certificate API can be reached. Exposure depends on the agent API being reachable by an attacker without a valid ACL token; the sources do not say how it is reached by default. Teams on versions outside that range can skip it.
No product ranges from the sources yet.
consul version on each agent and server and compare against the fixed versions.2.1.0.2.1.0, or 1.21.19 on the 1.x line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
HashiCorp Consul and Consul Enterprise 1.17.0 up to 2.0.4 are vulnerable to an authorization bypass in the agent's service mesh leaf certificate API that may allow an attacker without a valid ACL token to retrieve a cached service leaf certificate and its private key. This vulnerability (CVE-2026-105765) is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
This page as .md · .json · in your agent: get_signal("CVE-2026-105765")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.