Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HashiCorp Consul and Consul Enterprise are affected, and an attacker without a valid access token could exploit this flaw to retrieve a cached service certificate and its private key, potentially allowing them to impersonate that service within the service mesh.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- HashiCorp Consul
From 1.17.0 · fixed in 2.1.0
- HashiCorp Consul Enterprise
From 1.17.0 · fixed in 2.1.0