consul-k8s ACL flaw can grant elevated Consul privileges (CVE-2026-110720)
An attacker must already create a ServiceAccount in another namespace and reach the Consul API; active exploitation is not confirmed.
64
Vulnerability1 · 1 read
CVE-2026-110720
Cross-namespace ACL bypass in Consul-k8s 0.42.0+
- CVSS 3.1
- 9.9 critical
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Consul-k8s 0.42.0 and later mishandle component ACL binding rules, allowing a cross-namespace authorization bypass. A low-privileged attacker on the network can trigger it without user interaction and obtain elevated Consul privileges. Clusters running those consul-k8s versions are affected until upgraded.
What to do: Upgrade consul-k8s to 1.8.18 or 2.1.0, which HashiCorp states fix CVE-2026-110720.
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorp consul-k8s | 0.42.0 and later | 1.8.18 and 2.1.0 |
Estimated exposure
No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-863
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
In the news
2 storiesHashiCorp patches Consul-k8s cross-namespace ACL bypass (CVE-2026-110720)
Versions 0.42.0 through 2.0.4 are affected only with system ACL management on; fixes are 1.8.18 and 2.1.0.
58