Is CVE-2026-87107 exploited in the wild?

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

How severe is CVE-2026-87107?

Medium severity, with a CVSS score of 5.4, published 10 September 2026.

Which products and versions are affected?

HashiCorp Consul 1.21.0 through 2.0.3; HashiCorp Consul Enterprise 1.21.0 through 2.0.3.

Is there a fix for CVE-2026-87107?

A patch was published on 2026-09-10: Fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-87107 attacked?

It is attacked with local access, in a hosted service.

Am I affected by CVE-2026-87107?

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.

CVE-2026-87107: HashiCorp Consul authorization bypass in catalog deregistration

CVE-2026-87107 · Severity: medium · CVSS 5.4 · Published 2026-09-10

HashiCorp Consul is a service discovery and networking platform used to manage microservices in distributed clusters. An authorization flaw allows users with limited write permissions to delete services and nodes imported from peered clusters they should not have access to, potentially disrupting service discovery and cross-cluster routing without proper access controls.

Technologies: HashiCorp Consul, HashiCorp Consul Enterprise. Vendors: HashiCorp.

Quick answers

Is CVE-2026-87107 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-87107 being exploited in the wild.
How severe is CVE-2026-87107?: Medium severity, with a CVSS score of 5.4, published 10 September 2026.
Which products and versions are affected?: HashiCorp Consul 1.21.0 through 2.0.3; HashiCorp Consul Enterprise 1.21.0 through 2.0.3.
Is there a fix for CVE-2026-87107?: A patch was published on 2026-09-10: Fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-87107 attacked?: It is attacked with local access, in a hosted service.
Am I affected by CVE-2026-87107?: 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.

Technical details

The catalog deregistration endpoint in Consul failed to properly enforce ownership boundaries between locally managed catalog objects and those imported through cluster peering. An attacker holding a local ACL token with service:write or node:write permissions could craft a deregistration request to remove peer-imported services, checks, or nodes outside their authorization scope. This requires an active cluster peering relationship and local write access, but allows deletion of resources the attacker should not control. The vulnerability affects Consul and Consul Enterprise versions 1.21.0 through 2.0.3 and is fixed in Consul 2.0.4 and Enterprise 1.21.18, 1.22.12, and 2.0.4.

Affected products

HashiCorp Consul 1.21.0 through 2.0.3
HashiCorp Consul Enterprise 1.21.0 through 2.0.3

Timeline

2026-09-10: disclosed: Published in HCSEC-2026-36
2026-09-10: patched: Fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4

References

https://discuss.hashicorp.com/t/hcsec-2026-36-consul-vulnerable-to-an-authorization-bypass-in-the-catalog-deregistration-path/77738

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