CVE-2026-87090: CWE-863: Incorrect Authorization in HashiCorp Consul
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.
AI Analysis
Technical Summary
CVE-2026-87090 is an incorrect authorization vulnerability (CWE-863) affecting HashiCorp Consul and Consul Enterprise. The issue exists in the catalog node-write path, where an attacker with node-write permission on one node can bypass authorization controls to delete another node's catalog registration and take over its identity, provided they know the node ID of the target node. This could lead to impersonation of nodes within the Consul service catalog. The vulnerability has a CVSS 3.1 score of 8.3, indicating high severity. Official patches are available in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4.
Potential Impact
An attacker with valid node-write permissions on any single node and knowledge of another node's ID can delete that node's catalog registration and assume its identity. This could lead to unauthorized actions performed under the guise of the impersonated node, potentially impacting service discovery and trust within the Consul environment. The vulnerability affects confidentiality (low), integrity (high), and availability (high) as per the CVSS vector.
Mitigation Recommendations
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.
CVE-2026-87090: CWE-863: Incorrect Authorization in HashiCorp Consul
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.
CVSS v3.1
Score 8.3high
Affected software
HashiCorp
Consul
HashiCorp
Consul Enterprise
pkg:github/Consul EnterpriseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-87090 is an incorrect authorization vulnerability (CWE-863) affecting HashiCorp Consul and Consul Enterprise. The issue exists in the catalog node-write path, where an attacker with node-write permission on one node can bypass authorization controls to delete another node's catalog registration and take over its identity, provided they know the node ID of the target node. This could lead to impersonation of nodes within the Consul service catalog. The vulnerability has a CVSS 3.1 score of 8.3, indicating high severity. Official patches are available in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4.
Potential Impact
An attacker with valid node-write permissions on any single node and knowledge of another node's ID can delete that node's catalog registration and assume its identity. This could lead to unauthorized actions performed under the guise of the impersonated node, potentially impacting service discovery and trust within the Consul environment. The vulnerability affects confidentiality (low), integrity (high), and availability (high) as per the CVSS vector.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- HashiCorp
- Date Reserved
- 2026-09-08T19:58:12.912Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aa2fed1d29482f9abff9624
Added to database: 09/10/2026, 19:02:41 UTC
Last enriched: 09/10/2026, 19:16:30 UTC
Last updated: 09/10/2026, 19:23:33 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.