CVE-2026-87090: HashiCorp Consul · Incorrect Authorization
Affects HashiCorp ConsulSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 2.0.4 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.4, 1.21.18
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade Consul and Consul Enterprise to 2.0.4; Consul Enterprise to 1.21.18.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorpConsul | Affected
| Fixed in
|
| HashiCorpConsul Enterprise | Affected
| Fixed in
|
GitHubConsulpkg:github/ConsulOther threats | Affected
| Fixed in
|
GitHubConsul Enterprisepkg:github/Consul EnterpriseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4. Users should upgrade to these versions or later to remediate the issue. No other mitigation or workaround is indicated in the available data.
Description
Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog node-write path that may allow an authenticated attacker to delete another node's catalog registration and take over its node identity. An attacker with a token granting node-write permission on any single node name may exploit this issue if they can obtain the node ID of a node they do not control. This vulnerability (CVE-2026-87090) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4.