Skip to content
Heist/ feed
Back to feed
UnratedFix available

HCSEC-2026-36 - Consul vulnerable to an authorization bypass in the catalog deregistration path

Type: patchSources: HashiCorp discuss security

A catalog deregistration authorization bypass may let a local ACL token remove peer-imported catalog objects. Exploitation requires active cluster peering and a local ACL token with write access to catalog resources; deployments without cluster peering are not affected.

Products
Consul, Consul Enterprise
Affected versions
1.21.0 through 2.0.3
Fixed versions
1.21.18, 1.22.12, 2.0.4
CVEs
CVE-2026-87107
Confirmed fixed CVEs
CVE-2026-87107
Updated in this feed
1 Nov 2026, 18:20 UTC · Revision 1

Source evidence

HCSEC-2026-36 - Consul vulnerable to an authorization bypass in the catalog deregistration path

official-hashicorp-discuss-security · Original source

Published 10 Sept 2026, 18:47 UTC

A catalog deregistration authorization bypass may let a local ACL token remove peer-imported catalog objects. Exploitation requires active cluster peering and a local ACL token with write access to catalog resources; deployments without cluster peering are not affected.

A caller with service:write or node:write permission may exploit this issue to remove services, checks, or nodes imported from a peered cluster without holding authority over the peer origin.

Consul

Fixed versions: 2.0.4

Prerequisites: an active cluster peering relationship and a local ACL token with write access to catalog resources

Consul Enterprise

Fixed versions: 1.21.18, 1.22.12, 2.0.4

Prerequisites: an active cluster peering relationship and a local ACL token with write access to catalog resources

Complete source record
{
  "id": "8a8ffe78db1a66e46b62072c6968e79958ed9dc27f862fa2d69241f1257187f9",
  "url": "https://discuss.hashicorp.com/t/hcsec-2026-36-consul-vulnerable-to-an-authorization-bypass-in-the-catalog-deregistration-path/77738",
  "method": "llm",
  "payload": {
    "kind": "patch",
    "title": "HCSEC-2026-36 - Consul vulnerable to an authorization bypass in the catalog deregistration path",
    "summary": "A catalog deregistration authorization bypass may let a local ACL token remove peer-imported catalog objects. Exploitation requires active cluster peering and a local ACL token with write access to catalog resources; deployments without cluster peering are not affected.",
    "evidence": "A caller with service:write or node:write permission may exploit this issue to remove services, checks, or nodes imported from a peered cluster without holding authority over the peer origin.",
    "products": [
      {
        "name": {
          "value": "Consul",
          "evidence": "Consul and Consul Enterprise 1.21.0 through 2.0.3; fixed in Consul 2.0.4"
        },
        "prerequisites": [
          {
            "value": "an active cluster peering relationship and a local ACL token with write access to catalog resources",
            "evidence": "Exploiting this issue requires an active cluster peering relationship and a local ACL token with write access to catalog resources."
          }
        ],
        "fixed_versions": [
          {
            "value": "2.0.4",
            "evidence": "fixed in Consul 2.0.4"
          }
        ],
        "affected_versions": [
          {
            "value": "1.21.0 through 2.0.3",
            "evidence": "Consul and Consul Enterprise 1.21.0 through 2.0.3; fixed in Consul 2.0.4"
          }
        ]
      },
      {
        "name": {
          "value": "Consul Enterprise",
          "evidence": "Consul and Consul Enterprise 1.21.0 through 2.0.3; fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12, and 2.0.4."
        },
        "prerequisites": [
          {
            "value": "an active cluster peering relationship and a local ACL token with write access to catalog resources",
            "evidence": "Exploiting this issue requires an active cluster peering relationship and a local ACL token with write access to catalog resources."
          }
        ],
        "fixed_versions": [
          {
            "value": "1.21.18",
            "evidence": "Consul Enterprise 1.21.18, 1.22.12, and 2.0.4."
          },
          {
            "value": "1.22.12",
            "evidence": "Consul Enterprise 1.21.18, 1.22.12, and 2.0.4."
          },
          {
            "value": "2.0.4",
            "evidence": "Consul Enterprise 1.21.18, 1.22.12, and 2.0.4."
          }
        ],
        "affected_versions": [
          {
            "value": "1.21.0 through 2.0.3",
            "evidence": "Consul and Consul Enterprise 1.21.0 through 2.0.3; fixed in Consul 2.0.4"
          }
        ]
      }
    ],
    "severity": "unknown",
    "fixed_cves": [
      {
        "cve": "CVE-2026-87107",
        "product": "Consul",
        "evidence": "This vulnerability (CVE-2026-87107) is fixed in Consul 2.0.4"
      },
      {
        "cve": "CVE-2026-87107",
        "product": "Consul Enterprise",
        "evidence": "This vulnerability (CVE-2026-87107) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4."
      }
    ],
    "related_cves": [
      {
        "value": "CVE-2026-87107",
        "evidence": "This vulnerability (CVE-2026-87107) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4."
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "official-hashicorp-discuss-security",
  "document_id": 24006,
  "published_at": "2026-09-10T18:47:55+00:00"
}