CVE-2026-105608
Description
A flaw was found in HashiCorp Consul. An authenticated user with service write permissions can bypass authorization controls during service mesh proxy registration. By applying custom Envoy proxy configurations without possessing required mesh write privileges, an attacker can alter proxy settings beyond their authorized scope, leading to privilege escalation.
Statement
Important: This flaw is assessed as having Important severity because authenticated actors possessing standard service registration permissions can circumvent authorization checks to inject arbitrary Envoy proxy settings, impacting the confidentiality and integrity of service mesh communications. Although exploitation requires existing service-level access, it exceeds expected privileges by modifying mesh-wide routing behavior without holding administrative credentials. In Red Hat Enterprise Linux environments, client integrations containing Consul libraries do not execute the affected Consul server service mesh registration service.
Mitigation
--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce mesh:write authorization on all alternate key spellings and encodings during Consul service mesh proxy registration: upgrade to Consul Community Edition 2.1.0, Consul Enterprise 2.1.0 / 1.21.19 (or the fixed Grafana builds), which enforce mesh:write authorization checks across all alternate key spellings and encodings for Envoy escape-hatch configurations during proxy registration, closing all 2 injection vectors (crafted key spellings for Envoy escape-hatch configuration, alternate key encodings bypassing permission verification). Until patched, this is a concern on Consul service mesh deployments where authenticated users have service:write permissions on a proxy and destination service, so Restrict network access to the Consul service registration API and audit accounts holding service:write permissions on proxies and destination services. As a compensating measure, Detect unauthorized Envoy proxy configurations applied during service mesh proxy registration by flagging drift against declared IaC baselines and Capture and forward Consul service registration API calls to a SIEM to detect proxy registration payloads containing alternate escape-hatch keys. These controls limit blast radius and contain exploitation, but they do not fix the underlying authorization bypass defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1007 Application Configuration Drift Detection (IaC Enforcement) (medium)
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.8 | N/A | 8.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Access Control
Technical Impact: Gain Privileges or Assume Identity
A user can access restricted functionality and/or sensitive information that may include administrative functionality and user accounts.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
