Is CVE-2026-110720 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-110720 being exploited in the wild.

How severe is CVE-2026-110720?

Critical severity, with a CVSS score of 9.9, published 26 October 2026.

Which products and versions are affected?

HashiCorp Consul-k8s 0.42.0 through 2.0.4.

How is CVE-2026-110720 attacked?

It is attacked over the network.

Am I affected by CVE-2026-110720?

Check whether you run HashiCorp Consul-k8s at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-110720: HashiCorp Consul-k8s authorization bypass in ACL binding rules

CVE-2026-110720 · Severity: critical · CVSS 9.9 · Published 2026-10-26

Consul-k8s is a Kubernetes integration for HashiCorp Consul, which manages service networking and authentication in containerized environments. Versions 0.42.0 through 2.0.4 fail to properly restrict ACL binding rules to the correct Kubernetes namespace, allowing an attacker with permissions in another namespace to impersonate a Consul component and gain elevated privileges. An attacker could use this to access or modify service configurations across the entire Consul deployment.

Vendors: HashiCorp.

Quick answers

Is CVE-2026-110720 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110720 being exploited in the wild.
How severe is CVE-2026-110720?: Critical severity, with a CVSS score of 9.9, published 26 October 2026.
Which products and versions are affected?: HashiCorp Consul-k8s 0.42.0 through 2.0.4.
Is there a fix for CVE-2026-110720?: Yes: fixed in Consul-k8s 1.8.18, 2.1.0. Until then: This vulnerability only affects deployments with system ACL management enabled (global.acls.manageSystemACLs=true); disabling this setting eliminates the risk until an upgrade is possible. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110720 attacked?: It is attacked over the network.
Am I affected by CVE-2026-110720?: Check whether you run HashiCorp Consul-k8s at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Consul-k8s 1.8.18, 2.1.0

This vulnerability only affects deployments with system ACL management enabled (global.acls.manageSystemACLs=true); disabling this setting eliminates the risk until an upgrade is possible.

Technical details

The vulnerability is an authorization bypass in ACL binding rules that affects deployments with system ACL management enabled (global.acls.manageSystemACLs=true). An attacker requires Kubernetes permissions to create a ServiceAccount in a non-Consul namespace, obtain its token, and have network access to the Consul API; they can then authenticate as a Consul component to obtain its associated privileges. The issue stems from binding rules not consistently restricting authentication to ServiceAccounts in the Consul deployment's namespace.

Affected products

HashiCorp Consul-k8s 0.42.0 through 2.0.4

Timeline

2026-10-26: disclosed: CVE-2026-110720 published

References

https://discuss.hashicorp.com/t/hcsec-2026-50-consul-k8s-vulnerable-to-a-cross-namespace-authorization-bypass-in-component-acl-binding-rules/77915

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.