CVE-2026-105765

Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API

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

Analysis

AI-generated

Technical impact

HashiCorp Consul and Consul Enterprise versions 1.17.0 through 2.0.4 contain an authorization bypass in the agent's Service Mesh leaf certificate API. An attacker without a valid ACL token can use the exposed endpoint to retrieve a cached service leaf certificate and its private key. The disclosure of these cryptographic credentials can compromise confidentiality and integrity of the Consul service mesh.

Affected Systems

Vulnerable builds include HashiCorp Consul Community Edition and Consul Enterprise. All releases starting with version 1.17.0 up to and including 2.0.4 are affected. The fix is delivered in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.

Risk and Exploitability

The CVSS score of 7.5 classifies this vulnerability as high severity. The EPSS score of < 1% indicates a very low likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known public exploits. The likely attack vector is via the exposed Service Mesh leaf certificate API. An attacker who can reach the API endpoint bypasses ACL checks and obtains the private key of a service leaf, exposing the confidentiality of the cryptographic material and potentially undermining the integrity of the service mesh. However, no exploits have been observed to date.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Consul Community Edition 2.1.0 or Consul Enterprise 2.1.0 or 1.21.19 to apply the vendor fix.
  • If an immediate upgrade is not possible, restrict network access to the Service Mesh leaf certificate API and enforce ACL policies that deny anonymous requests.
  • Audit existing leaf certificates for compromise and rotate them to new keys to prevent use of potentially leaked credentials.

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': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title HCSEC-2026-46 - Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API
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 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.
Title HCSEC-2026-46 - Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API
Weaknesses CWE-862
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-524

    Use of Cache Containing Sensitive Information

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
HashiCorp
Published
Updated
Nov 2, 2026, 7:43 PM
Reserved
Oct 5, 2026, 7:12 PM
Status
Awaiting Analysis
Published
Oct 26, 2026, 6:17 PM
Modified
Nov 2, 2026, 8:17 PM
Severity
Important
Public date
Oct 26, 2026, 5:42 PM