CVE-2026-110720
Received Received - Intake

Cross-Namespace ACL Bypass in Consul-K8s

Vulnerability report for CVE-2026-110720, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-26

Last updated on: 2026-10-26

Assigner: HashiCorp Inc.

Description

Consul-k8s versions 0.42.0 and later are vulnerable to a cross-namespace authorization bypass in component ACL binding rules that may allow an attacker to obtain elevated Consul privileges. This vulnerability (CVE-2026-110720) is fixed in consul-k8s 2.1.0 and 1.8.18.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-26
Last Modified
2026-10-26
Generated
2026-10-26
AI Q&A
2026-10-26
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
HashiCorp Tooling 0.42.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-110720 is a cross-namespace authorization bypass in HashiCorp's consul-k8s software versions 0.42.0 and later. It allows an attacker to gain elevated Consul privileges by exploiting improper authentication of Kubernetes ServiceAccounts from other namespaces when system ACL management is enabled.

Detection Guidance

To detect this vulnerability, check if your consul-k8s version is between 0.42.0 and 2.0.4. Verify if system ACL management is enabled by inspecting the global.acls.manageSystemACLs setting in your Consul configuration. Ensure no unauthorized ServiceAccounts from other namespaces have access to the Consul API.

Impact Analysis

An attacker with Kubernetes permissions to create a ServiceAccount and obtain its token in a different namespace, along with network access to the Consul API, could exploit this flaw to authenticate as a Consul component and acquire its associated privileges.

Mitigation Strategies

Upgrade consul-k8s to version 2.1.0 or 1.8.18 immediately. If upgrading is not possible, disable system ACL management by setting global.acls.manageSystemACLs=false. Review and restrict Kubernetes ServiceAccount permissions to prevent unauthorized access to the Consul API.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110720. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart