Consul-k8s lets attackers gain extra Consul privileges across namespaces
A flaw in the software that connects HashiCorp Consul to Kubernetes can let someone reach permissions they should not have, crossing the boundaries between separate Kubernetes namespaces. Updating closes the gap.
| Severity | CriticalCVSS 9.9 of 10 |
|---|---|
| Being exploited? | UnclearNo reports either way yet |
| Fix available? | Yesconsul-k8s 2.1.0 and 1.8.18 · since 26 Oct 2026 |
| How sure is this? | Official sourceBacked by an official source |
What happened
Consul-k8s versions 0.42.0 and later have a cross-namespace authorization bypass in component ACL binding rules, which may allow an attacker to obtain elevated Consul privileges.
Are you affected?
You are affected if you run consul-k8s version 0.42.0 or later in a Kubernetes environment with Consul ACLs.
consul-k8s 0.42.0 and later (before the fixed versions below)
What to do
- Update consul-k8s to 2.1.0 or to 1.8.18, matching your release line
- Review Consul ACL and component binding rules for unexpected cross-namespace permissions
- Check Consul audit logs for unexpected privilege changes
Timeline
- 26 Oct 2026, 19:16 UTCPublicly disclosed
- 26 Oct 2026, 19:16 UTCReported by NVD · NVD
- 26 Oct 2026, 19:17 UTCPicked up by Zero Radar
Sources 1 report, oldest first
Official vendor, government CERT or advisory database
- CVE-2026-110720NVD · 26 Oct 2026, 19:16 UTC
Technical details
- ID
- CVE-2026-110720
- CVSS
- 9.9 / 10
- EPSS
- 0.4% chance of exploitation within 30 days
- Disclosed
- 26 Oct 2026, 19:16 UTC
- On Zero Radar
- 26 Oct 2026, 19:17 UTC (1 min after disclosure)
- Last change
- 26 Oct 2026, 19:17 UTC
The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works