Signal is active with 3 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
STABLE
⚠️ CVE-2026-110720 (9.9) ⚠️ consul-k8s, which runs Consul on Kubernetes, lets an attacker with access in one namespace gain elevated Consul privileges in another. consul-k8s 0.42.0 and later is affected. Upgrade to 2.1.0 or 1.8.18. https://t.co/2z1F61B9Qr
Patch CVE-2026-110720 now. This 9.9 CVSS consul-k8s vulnerability enables a cross-namespace authorization bypass in ACL binding rules. #HashiCorp #Consul #Kubernetes #CVE2026110720 #CloudSecurity #Cybersecurity #Vulnerability #InfoSec https://securityonline.info/hashicorp-consul-k8s-vulnerability-cve-2026-110720/
Consul-k8s CVE-2026-110720: ACL binding rules didn't always pin the namespace. Create a ServiceAccount in another namespace, reach the Consul API, get a component's privileges. Upgrade to 2.1.0/1.8.18. Audit k8s auth roles: bind name AND namespace. https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915
🚨Critical - Consul-k8s Cross-Namespace ACL Binding Bypass (CVE-2026-110720) consul-k8s ACL binding rules allow a cross-namespace authorization bypass, letting a pod/service account influence bindings outside its namespace and obtain elevated Consul ACL privileges. Impacts Consul access control, not just Kubernetes RBAC. 👉Affected: consul-k8s >= 0.42.0 | Upgrade to 2.1.0 or 1.8.18