High severity · published Jun 6, 2019
CVE-2019-12291
HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control
7.5
CVSS
1.2%
EPSS
No
On KEV
Description
HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control. Keys not matching a specific ACL rule used for prefix matching in a policy can be deleted by a token using that policy even with default deny settings configured.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
None
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.2% · higher than 67% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CO
Consul · Hashicorp
1.4.0 through 1.5.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-12291
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-12291
Issue Tracking
https://github.com/hashicorp/consul/issues/5888
More from Consul
8.8
CVE-2026-105608
Consul vulnerable to an authorization bypass in service mesh registration
8.8
CVE-2021-41805
HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4 has Incorrect Access Control
8.8
CVE-2021-37219
HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling…
8.6
CVE-2021-3121
An issue was discovered in GoGo Protobuf before 1.3.2
8.3
CVE-2026-87090
Consul vulnerable to an authorization bypass in the catalog node-write path