CVE-2026-105608

Consul vulnerable to an authorization bypass in service mesh registration

Published Oct 26, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

This vulnerability is located in HashiCorp Consul’s service mesh proxy registration code. A user who has service write rights, but not the required mesh write permission, can inject an Envoy escape‑hatch configuration, effectively bypassing the intended authorization controls. The result is the ability to modify Envoy settings for a service without proper authority, which could allow an attacker to alter traffic flow or facilitate lateral movement within a cluster. The weakness is a permission validation error (CWE‑178) and an insufficient authorization flaw (CWE‑267).

Affected Systems

HashiCorp Consul Community Edition versions prior to 2.1.0 and HashiCorp Consul Enterprise versions prior to 2.1.0 and 1.21.19 are affected. Users of older releases that have not applied the points‑in‑fix for Consul’s service mesh registration must review their version roll‑up status.

Risk and Exploitability

The CVSS severity score of 8.8 classifies this as a high‑impact flaw that requires careful mitigation. The EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, but that does not diminish the risk to environments that grant service write permissions. The attacker must be able to write to the service configuration, a privilege often granted to internal services or automated processes; thus the most likely attack vector is an internal compromise or mis‑configuration that bestows write access to a legitimate user or process.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HashiCorp Consul to Community Edition 2.1.0 or Consul Enterprise to either 2.1.0 or 1.21.19, which contain the authorization fix.
  • Restrict the scope of service write permissions in your cluster, ensuring that only trusted services or administrators can modify service configurations. Apply the principle of least privilege to service roles.
  • Validate that all Envoy escape‑hatch configurations are only introduced by authenticated mesh‑write operations, and audit configuration changes regularly for unauthorized modifications.

Generated by OpenCVE AI on November 3, 2026 at 01:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Vendors & Products Hashicorp
Hashicorp consul
Hashicorp consul Enterprise
Type Values Removed Values Added
Description 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.
Title Consul vulnerable to an authorization bypass in service mesh registration
Weaknesses CWE-178
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-178

    Improper Handling of Case Sensitivity

  • CWE-267

    Privilege Defined With Unsafe Actions

Sources

Status
PUBLISHED
Assigner
HashiCorp
Published
Updated
Oct 26, 2026, 7:38 PM
Reserved
Oct 5, 2026, 4:15 PM
Status
Awaiting Analysis
Published
Oct 26, 2026, 6:17 PM
Modified
Oct 26, 2026, 8:17 PM
Severity
Important
Public date
Oct 26, 2026, 5:52 PM