VYPR

Consul

by Hashicorp

Source repositories

CVEs (54)

  • CVE-2026-2808MedMar 12, 2026
    risk 0.44cvss 6.8epss 0.01

    HashiCorp Consul and Consul Enterprise 1.18.20 up to 1.21.10 and 1.22.4 are vulnerable to arbitrary file read when configured with Kubernetes authentication. This vulnerability, CVE-2026-2808, is fixed in Consul 1.18.21, 1.21.11 and 1.22.5.

  • CVE-2026-105765HigOct 26, 2026
    risk 0.42cvss 7.5epss 0.00

    HashiCorp Consul and Consul Enterprise 1.17.0 up to 2.0.4 are vulnerable to an authorization bypass in the agent's service mesh leaf certificate API that may allow an attacker without a valid ACL token to retrieve a cached service leaf certificate and its private key. This…

  • CVE-2026-105626HigOct 26, 2026
    risk 0.42cvss 7.5epss 0.00

    HashiCorp Consul and Consul Enterprise are vulnerable to a denial of service in the HTTP API that may allow an unauthenticated attacker to exhaust memory on a Consul agent. This vulnerability (CVE-2026-105626) is fixed in Consul Community Edition 2.1.0 and Consul Enterprise…

  • CVE-2022-24687MedFeb 24, 2022
    risk 0.42cvss 6.5epss 0.01

    HashiCorp Consul and Consul Enterprise 1.9.0 through 1.9.14, 1.10.7, and 1.11.2 clusters with at least one Ingress Gateway allow a user with service:write to register a specifically-defined service that can cause Consul servers to panic. Fixed in 1.9.15, 1.10.8, and 1.11.3.

  • CVE-2021-38698MedSep 7, 2021
    risk 0.42cvss 6.5epss 0.01

    HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.

  • CVE-2020-13250HigJun 11, 2020
    risk 0.42cvss 7.5epss 0.03

    HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service. Fixed in 1.6.6 and 1.7.4.

  • CVE-2020-13170HigJun 11, 2020
    risk 0.42cvss 7.5epss 0.02

    HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

  • CVE-2020-12758HigJun 11, 2020
    risk 0.42cvss 7.5epss 0.02

    HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4.

  • CVE-2019-12291HigJun 6, 2019
    risk 0.42cvss 7.5epss 0.01

    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.

  • CVE-2019-9764HigMar 26, 2019
    risk 0.41cvss 7.4epss 0.01

    HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication. In other words, the product behaves as if verify_server_hostname were set to false, even when it is actually set to true. This is fixed in 1.4.4.

  • CVE-2020-25864MedApr 20, 2021
    risk 0.40cvss 6.1epss 0.06

    HashiCorp Consul and Consul Enterprise up to version 1.9.4 key-value (KV) raw mode was vulnerable to cross-site scripting. Fixed in 1.9.5, 1.8.10 and 1.7.14.

  • CVE-2026-88021HigSep 10, 2026
    risk 0.39cvss 7.1epss 0.00

    Consul and Consul Enterprise are vulnerable to an authorization bypass in the Connect service mesh that may allow a service to reach a destination it is not authorized to access. When building Envoy RBAC rules to enforce Connect intentions, Consul did not correctly escape…

  • CVE-2023-5332MedDec 4, 2023
    risk 0.38cvss 5.9epss 0.01

    Patch in third party library Consul requires 'enable-script-checks' to be set to False. This was required to enable a patch by the vendor. Without this setting the patch could be bypassed. This only affects GitLab-EE.

  • CVE-2026-19017MedAug 7, 2026
    risk 0.37cvss 6.8epss 0.00

    Consul Community Edition and Consul Enterprise 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to use the Vault Connect CA provider with JWT or AppRole authentication. A privileged attacker with `operator:write` permission may direct Consul…

  • CVE-2026-115804MedOct 26, 2026
    risk 0.35cvss 6.4epss 0.00

    HashiCorp Consul and Consul Enterprise are vulnerable to an authorization bypass in health check registration that may allow an authenticated user to modify health checks belonging to another service on the same node. This vulnerability (CVE-2026-115804) is fixed in Consul…

  • CVE-2026-87106MedSep 10, 2026
    risk 0.35cvss 6.5epss 0.00

    Consul and Consul Enterprise are vulnerable to a denial of service in the native RPC listener that may allow an authenticated client to exhaust server memory before ACL authorization is evaluated. A client that can complete the internal RPC mTLS handshake may exploit this issue…

  • CVE-2025-11375MedOct 28, 2025
    risk 0.35cvss 6.5epss 0.00

    Consul and Consul Enterprise’s (“Consul”) event endpoint is vulnerable to denial of service (DoS) due to lack of maximum value on the Content Length header. This vulnerability, CVE-2025-11375, is fixed in Consul Community Edition 1.22.0 and Consul Enterprise 1.22.0,…

  • CVE-2025-11374MedOct 28, 2025
    risk 0.35cvss 6.5epss 0.00

    Consul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS) due to incorrect Content Length header validation. This vulnerability, CVE-2025-11374, is fixed in Consul Community Edition 1.22.0 and Consul Enterprise 1.22.0, 1.21.6,…

  • CVE-2022-40716MedSep 23, 2022
    risk 0.35cvss 6.5epss 0.01

    HashiCorp Consul and Consul Enterprise up to 1.11.8, 1.12.4, and 1.13.1 do not check for multiple SAN URI values in a CSR on the internal RPC endpoint, enabling leverage of privileged access to bypass service mesh intentions. Fixed in 1.11.9, 1.12.5, and 1.13.2."

  • CVE-2020-28053MedNov 23, 2020
    risk 0.35cvss 6.5epss 0.01

    HashiCorp Consul and Consul Enterprise 1.2.0 up to 1.8.5 allowed operators with operator:read ACL permissions to read the Connect CA private key configuration. Fixed in 1.6.10, 1.7.10, and 1.8.6.