Live › vulnerability › CVE-2026-105608
Go to dashboardConsul and Consul Enterprise let a user with service write permission apply Envoy escape-hatch proxy configuration without the mesh write permission that should be required. An attacker with limited service-level access can change how service mesh proxies are configured.
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 or Consul Enterprise with service mesh enabled, where some users or tokens hold service write permission. Deployments without service mesh proxy registration, or where only fully trusted operators can write services, face less risk. unknown whether the sources name a specific default configuration.
No product ranges from the sources yet.
consul version and compare it against the fixed releases listed in the fix field.2.1.0.2.1.0 or 1.21.19, depending on the release line in use.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
HashiCorp Consul and Consul Enterprise are vulnerable to an authorization bypass in service mesh proxy registration. This may allow a user with service write permission to apply Envoy escape-hatch configuration without the required mesh write permission. This vulnerability (CVE-2026-105608) 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-105608")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.