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