CVE-2019-12291
mediumpriority · track · 30EPSS 0.012 · 67 %ileEUUSEPSS · scored 2026-10-27
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
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.4–7.5
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (3)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- GHSA-h65h-v7fw-4p38HashiCorp Consul Incorrect Access Control vulnerability2023-06-09ghsa · osvUS
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. ### Specific Go Packages Affected github.com/hashicorp/consul/acl
- GO-2023-1852HashiCorp Consul Incorrect Access Control vulnerability in github.com/hashicorp/consul2024-08-20vendor · osvUS
HashiCorp Consul Incorrect Access Control vulnerability in github.com/hashicorp/consul
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (4)
External citations — patches, advisories, analysis.
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan