# CVE-2026-115804: HashiCorp Consul authorization bypass in health check registration

Source: https://junglewise.ai/threats/cve-2026-115804-hashicorp-consul-and-consul-enterprise-are-vulnerable-to-an  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-26. Updated: 2026-10-26  
License: CC BY 4.0 with a link back

CVE-2026-115804 · Severity: medium · CVSS 6.4 · Published 2026-10-26

HashiCorp Consul is a service discovery and networking platform used by enterprises to manage microservices. An authenticated user with permissions to one service can modify health checks belonging to a different service on the same node, potentially causing the affected service to be removed from service discovery or mesh routing. This requires ACLs to be enabled and write access to another service on the same node.

Technologies: [HashiCorp Consul](https://junglewise.ai/threats/technologies/consul), [HashiCorp Consul Enterprise](https://junglewise.ai/threats/technologies/consul-enterprise). Vendors: [HashiCorp](https://junglewise.ai/threats/vendors/hashicorp).

## Quick answers

**Is CVE-2026-115804 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-115804 being exploited in the wild.

**How severe is CVE-2026-115804?** Medium severity, with a CVSS score of 6.4, published 26 October 2026.

**Which products and versions are affected?** HashiCorp Consul 0.7.2 to 2.0.4; HashiCorp Consul Enterprise 0.7.2 to 2.0.4.

**Is there a fix for CVE-2026-115804?** Yes: fixed in Consul 2.1.0, Consul Enterprise 2.1.0 and 1.21.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-115804 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-115804?** Check whether you run HashiCorp Consul or HashiCorp Consul Enterprise 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 2.1.0, Consul Enterprise 2.1.0 and 1.21.19

## Technical details

Consul fails to consistently authorize health check modifications against the service the check is bound to. An authenticated attacker with service:write permission for one service can abuse this to modify or rebind health checks of a different service on the same node without proper authorization. This may alter the target service's health status and influence service discovery and mesh routing behavior.

## Affected products

- HashiCorp Consul 0.7.2 to 2.0.4
- HashiCorp Consul Enterprise 0.7.2 to 2.0.4

## Timeline

- 2026-10-26: disclosed

## References

- [https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914](https://discuss.hashicorp.com/t/hcsec-2026-49-consul-vulnerable-to-an-authorization-bypass-in-health-check-registration/77914)

## Related threats

- [HashiCorp Consul authorization bypass in service mesh leaf certificate API](https://junglewise.ai/threats/cve-2026-105765-hashicorp-consul-and-consul-enterprise-1-17-0-up-to-2-0-4-are)
- [HashiCorp Consul HTTP API denial of service](https://junglewise.ai/threats/cve-2026-105626-hashicorp-consul-and-consul-enterprise-are-vulnerable-to-a)
- [HashiCorp Consul authorization bypass in service mesh proxy registration](https://junglewise.ai/threats/cve-2026-105608-hashicorp-consul-and-consul-enterprise-are-vulnerable-to-an)
- [HashiCorp Consul authorization bypass in Connect service mesh](https://junglewise.ai/threats/cve-2026-88021-hashicorp-consul-authorization-bypass-in-connect-service-mesh)
- [HashiCorp Consul authorization bypass in catalog deregistration](https://junglewise.ai/threats/cve-2026-87107-hashicorp-consul-authorization-bypass-in-catalog-deregistration)