Hashicorp
187 vulnerabilities.
All published vulnerabilities with a CVE number in Hashicorp products, newest first, with severity and references.
Page 1 of 2
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2025-13432 | Hashicorp Terraform: Terraform state versions can be created by a user with specific but insufficient permissions in a Terraform Enterprise workspace. This may allow … | 2025-11-21 | 4.3 |
| CVE-2025-13357 | Hashicorp Terraform Provider: Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default, potentially resulting … | 2025-11-21 | 7.4 |
| CVE-2025-12044 | Hashicorp Vault: Vault and Vault Enterprise (“Vault”) are vulnerable to an unauthenticated denial of service when processing JSON payloads. This occurs due to a … | 2025-10-23 | 7.5 |
| CVE-2025-11621 | Hashicorp Vault: Vault and Vault Enterprise’s (“Vault”) AWS Auth method may be susceptible to authentication bypass if the role of the configured … | 2025-10-23 | 8.1 |
| CVE-2025-11375 | Hashicorp Consul: Consul and Consul Enterprise’s (“Consul”) event endpoint is vulnerable to denial of service (DoS) due to lack of maximum value on the Content … | 2025-10-28 | 6.5 |
| CVE-2025-11374 | Hashicorp Consul: Consul and Consul Enterprise’s (“Consul”) key/value endpoint is vulnerable to denial of service (DoS) due to incorrect Content Length header … | 2025-10-28 | 6.5 |
| CVE-2025-8959 | Hashicorp Go-getter: HashiCorp's go-getter library subdirectory download feature is vulnerable to symlink attacks leading to unauthorized read access beyond the … | 2025-08-15 | 7.5 |
| CVE-2025-6203 | Hashicorp Vault: A malicious user may submit a specially-crafted complex payload that otherwise meets the default request size limit which results in excessive … | 2025-08-28 | 7.5 |
| CVE-2025-6037 | Hashicorp Vault: Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA … | 2025-08-01 | 6.8 |
| CVE-2025-6015 | Hashicorp Vault: Vault and Vault Enterprise’s (“Vault”) login MFA rate limits could be bypassed and TOTP tokens could be reused. Fixed in Vault Community Edition … | 2025-08-01 | 5.7 |
| CVE-2025-6014 | Hashicorp Vault: Vault and Vault Enterprise’s (“Vault”) TOTP Secrets Engine code validation endpoint is susceptible to code reuse within its validity period. Fixed … | 2025-08-01 | 6.5 |
| CVE-2025-6013 | Hashicorp Vault: Vault and Vault Enterprise’s (“Vault”) ldap auth method may not have correctly enforced MFA if username_as_alias was set to true and a user had … | 2025-08-06 | 6.5 |
| CVE-2025-6011 | Hashicorp Vault: A timing side channel in Vault and Vault Enterprise’s (“Vault”) userpass auth method allowed an attacker to distinguish between existing and … | 2025-08-01 | 3.7 |
| CVE-2025-6004 | Hashicorp Vault: Vault and Vault Enterprise’s (“Vault”) user lockout feature could be bypassed for Userpass and LDAP authentication methods. Fixed in Vault … | 2025-08-01 | 5.3 |
| CVE-2025-6000 | Hashicorp Vault: A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a … | 2025-08-01 | 9.1 |
| CVE-2025-5999 | Hashicorp Vault: A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s token … | 2025-08-01 | 7.2 |
| CVE-2025-4922 | Hashicorp Nomad: Nomad Community and Nomad Enterprise (“Nomad”) prefix-based ACL policy lookup can lead to incorrect rule application and shadowing. This … | 2025-06-11 | 8.1 |
| CVE-2025-4656 | Hashicorp Vault: Vault Community and Vault Enterprise rekey and recovery key operations can lead to a denial of service due to uncontrolled cancellation by a Vault … | 2025-06-25 | 3.1 |
| CVE-2025-4166 | Hashicorp Vault: Vault Community and Vault Enterprise Key/Value (kv) Version 2 plugin may unintentionally expose sensitive information in server and audit logs when … | 2025-05-02 | 4.5 |
| CVE-2025-3879 | Hashicorp Vault: Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the … | 2025-05-02 | 6.6 |
| CVE-2025-3744 | Hashicorp Nomad: Nomad Enterprise (“Nomad”) jobs using the policy override option are bypassing the mandatory sentinel policies. This vulnerability, identified as … | 2025-05-13 | 7.6 |
| CVE-2025-1296 | Hashicorp Nomad: Nomad Community and Nomad Enterprise (“Nomad”) are vulnerable to unintentional exposure of the workload identity token and client secret token in … | 2025-03-10 | 6.5 |
| CVE-2025-1293 | Hashicorp Hermes: Hermes versions up to 0.4.0 improperly validated the JWT provided when using the AWS ALB authentication mode, potentially allowing for … | 2025-02-20 | 8.2 |
| CVE-2025-0937 | Hashicorp Nomad: Nomad Community and Nomad Enterprise ("Nomad") event stream configured with a wildcard namespace can bypass the ACL Policy allowing reads on other … | 2025-02-12 | 7.1 |
| CVE-2025-0377 | Hashicorp Go-slug: HashiCorp’s go-slug library is vulnerable to a zip-slip style attack when a non-existing user-provided path is extracted from the tar entry. | 2025-01-21 | 7.5 |
| CVE-2024-12678 | Hashicorp Nomad: Nomad Community and Nomad Enterprise ("Nomad") allocations are vulnerable to privilege escalation within a namespace through unredacted workload … | 2024-12-20 | 6.5 |
| CVE-2024-12289 | Hashicorp Boundary: Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the initialization of the Boundary … | 2024-12-12 | 5.9 |
| CVE-2024-10975 | Hashicorp Nomad: Nomad Community and Nomad Enterprise ("Nomad") volume specification is vulnerable to arbitrary cross-namespace volume creation through unauthorized … | 2024-11-07 | 7.7 |
| CVE-2024-10228 | Hashicorp Vagrant Vmware Utility: The Vagrant VMWare Utility Windows installer targeted a custom location with a non-protected path that could be modified by an unprivileged user, … | 2024-10-29 | 3.8 |
| CVE-2024-10086 | Hashicorp Consul: A vulnerability was identified in Consul and Consul Enterprise such that the server response did not explicitly set a Content-Type HTTP header, … | 2024-10-30 | 6.1 |
| CVE-2024-10006 | Hashicorp Consul: A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in L7 traffic intentions could bypass HTTP header … | 2024-10-30 | 8.3 |
| CVE-2024-10005 | Hashicorp Consul: A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using URL paths in L7 traffic intentions could bypass HTTP … | 2024-10-30 | 8.1 |
| CVE-2024-9180 | Openbao: A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s privileges … | 2024-10-10 | 7.2 |
| CVE-2024-8365 | Hashicorp Vault: Vault Community Edition and Vault Enterprise experienced a regression where functionality that HMAC’d sensitive headers in the configured audit … | 2024-09-02 | 6.2 |
| CVE-2024-8185 | Hashicorp Vault: Vault Community and Vault Enterprise (“Vault”) clusters using Vault’s Integrated Storage backend are vulnerable to a denial-of-service (DoS) attack … | 2024-10-31 | 7.5 |
| CVE-2024-7625 | Hashicorp Nomad: In HashiCorp Nomad and Nomad Enterprise from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2, the archive unpacking process is vulnerable to writes outside … | 2024-08-14 | 5.8 |
| CVE-2024-7594 | Hashicorp Vault: Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields … | 2024-09-26 | 7.5 |
| CVE-2024-6468 | Hashicorp Vault: Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, … | 2024-07-11 | 7.5 |
| CVE-2024-6257 | Hashicorp Go-getter: HashiCorp’s go-getter library can be coerced into executing Git update on an existing maliciously modified Git Configuration, potentially leading … | 2024-06-25 | 8.4 |
| CVE-2024-6104 | Hashicorp Retryablehttp: go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP … | 2024-06-24 | 6.0 |
| CVE-2024-5798 | Hashicorp Vault: Vault and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This … | 2024-06-12 | 2.6 |
| CVE-2024-3817 | Hashicorp Go-getter: HashiCorp’s go-getter library is vulnerable to argument injection when executing Git to discover remote branches. This vulnerability does not … | 2024-04-17 | 9.8 |
| CVE-2024-2877 | Hashicorp Vault: Vault Enterprise, when configured with performance standby nodes and a configured audit device, will inadvertently log request headers on the … | 2024-04-30 | 5.5 |
| CVE-2024-2660 | Hashicorp Vault: Vault and Vault Enterprise TLS certificates auth method did not correctly validate OCSP responses when one or more OCSP sources were configured. … | 2024-04-04 | 6.4 |
| CVE-2024-2048 | Hashicorp Vault: Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA … | 2024-03-04 | 8.1 |
| CVE-2024-1329 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 1.5.13 up to 1.6.6, and 1.7.3 template renderer is vulnerable to arbitrary file write on the host as the Nomad … | 2024-02-08 | 7.7 |
| CVE-2024-1052 | Hashicorp Boundary: Boundary and Boundary Enterprise (“Boundary”) is vulnerable to session hijacking through TLS certificate tampering. An attacker with privileges to … | 2024-02-05 | 8.0 |
| CVE-2024-0831 | Hashicorp Vault: Vault and Vault Enterprise (“Vault”) may expose sensitive information when enabling an audit device which specifies the `log_raw` option, which may … | 2024-02-01 | 4.5 |
| CVE-2023-25000 | Hashicorp Vault: HashiCorp Vault's implementation of Shamir's secret sharing used precomputed table lookups, and was vulnerable to cache-timing attacks. An attacker … | 2023-03-29 | 5.0 |
| CVE-2023-24999 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise’s approle auth method allowed any authenticated user with access to an approle destroy endpoint to destroy the … | 2023-03-10 | 4.4 |
| CVE-2023-6337 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise 1.12.0 and newer are vulnerable to a denial of service through memory exhaustion of the host when handling … | 2023-12-08 | 7.5 |
| CVE-2023-5954 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise inbound client requests triggering a policy check can lead to an unbounded consumption of memory. A large … | 2023-11-09 | 5.9 |
| CVE-2023-5834 | Hashicorp Vagrant: HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for … | 2023-10-27 | 3.8 |
| CVE-2023-5332 | Gitlab: 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 … | 2023-12-04 | 5.9 |
| CVE-2023-5077 | Hashicorp Vault: The Vault and Vault Enterprise ("Vault") Google Cloud secrets engine did not preserve existing Google Cloud IAM Conditions upon creating or … | 2023-09-28 | 7.6 |
| CVE-2023-4782 | Hashicorp Terraform: Terraform version 1.0.8 through 1.5.6 allows arbitrary file write during the `init` operation if run on maliciously crafted Terraform … | 2023-09-08 | 6.3 |
| CVE-2023-4680 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption … | 2023-09-14 | 6.8 |
| CVE-2023-3775 | Hashicorp Vault: A Vault Enterprise Sentinel Role Governing Policy created by an operator to restrict access to resources in one namespace can be applied to … | 2023-09-28 | 4.2 |
| CVE-2023-3774 | Hashicorp Vault: An unhandled error in Vault Enterprise's namespace creation may cause the Vault process to crash, potentially resulting in denial of service. Fixed … | 2023-07-27 | 4.9 |
| CVE-2023-3518 | Hashicorp Consul: HashiCorp Consul and Consul Enterprise 1.16.0 when using JWT Auth for service mesh incorrectly allows/denies access regardless of service … | 2023-08-09 | 7.4 |
| CVE-2023-3462 | Hashicorp Vault: HashiCorp's Vault and Vault Enterprise are vulnerable to user enumeration when using the LDAP auth method. An attacker may submit requests of … | 2023-07-31 | 5.3 |
| CVE-2023-3300 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 0.11.0 up to 1.5.6 and 1.4.1 HTTP search API can reveal names of available CSI plugins to unauthenticated … | 2023-07-19 | 5.3 |
| CVE-2023-3299 | Hashicorp Nomad: HashiCorp Nomad Enterprise 1.2.11 up to 1.5.6, and 1.4.10 ACL policies using a block without a label generates unexpected results. Fixed in 1.6.0, … | 2023-07-19 | 3.4 |
| CVE-2023-3114 | Hashicorp Terraform Enterprise: Terraform Enterprise since v202207-1 did not properly implement authorization rules for agent pools, allowing the workspace to be targeted by … | 2023-06-22 | 5.0 |
| CVE-2023-3072 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 0.7.0 up to 1.5.6 and 1.4.10 ACL policies using a block without a label generates unexpected results. Fixed in … | 2023-07-19 | 4.1 |
| CVE-2023-2816 | Hashicorp Consul: Consul and Consul Enterprise allowed any user with service:write permissions to use Envoy extensions configured via service-defaults to patch … | 2023-06-02 | 8.7 |
| CVE-2023-2197 | Hashicorp Vault: HashiCorp Vault Enterprise 1.13.0 up to 1.13.1 is vulnerable to a padding oracle attack when using an HSM in conjunction with the CKM_AES_CBC_PAD … | 2023-05-01 | 2.5 |
| CVE-2023-2121 | Hashicorp Vault: Vault and Vault Enterprise's (Vault) key-value v2 (kv-v2) diff viewer allowed HTML injection into the Vault web UI through key values. This … | 2023-06-09 | 4.3 |
| CVE-2023-1782 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise versions 1.5.0 up to 1.5.2 allow unauthenticated users to bypass intended ACL authorizations for clusters … | 2023-04-05 | 9.9 |
| CVE-2023-1299 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 1.5.0 allow a job submitter to escalate to management-level privileges using workload identity and task API. … | 2023-03-14 | 7.4 |
| CVE-2023-1297 | Hashicorp Consul: Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluster with service of the same name as a local … | 2023-06-02 | 4.9 |
| CVE-2023-1296 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.5.0 did not correctly enforce deny policies applied to a workload’s variables. Fixed in 1.4.6 … | 2023-03-14 | 2.7 |
| CVE-2023-0845 | Hashicorp Consul: Consul and Consul Enterprise allowed an authenticated user with service:write permissions to trigger a workflow that causes Consul server and … | 2023-03-09 | 4.9 |
| CVE-2023-0821 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 1.2.15 up to 1.3.8, and 1.4.3 jobs using a maliciously compressed artifact stanza source can cause excessive … | 2023-02-16 | 6.5 |
| CVE-2023-0690 | Hashicorp Boundary: HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in … | 2023-02-08 | 5.0 |
| CVE-2023-0665 | Hashicorp Vault: HashiCorp Vault's PKI mount issuer endpoints did not correctly authorize access to remove an issuer or modify issuer metadata, potentially … | 2023-03-29 | 6.5 |
| CVE-2023-0620 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise versions 0.8.0 through 1.13.1 are vulnerable to an SQL injection attack when configuring the Microsoft SQL … | 2023-03-29 | 6.5 |
| CVE-2023-0475 | Hashicorp Go-getter: HashiCorp go-getter up to 1.6.2 and 2.1.1 is vulnerable to decompression bombs. Fixed in 1.7.0 and 2.2.0. | 2023-02-16 | 4.2 |
| CVE-2022-42717 | Hashicorp Vagrant: An issue was discovered in Hashicorp Packer before 2.3.1. The recommended sudoers configuration for Vagrant on Linux is insecure. If the host has … | 2022-10-11 | 7.8 |
| CVE-2022-41606 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 1.0.2 up to 1.2.12, and 1.3.5 jobs submitted with an artifact stanza using invalid S3 or GCS URLs can be used … | 2022-10-11 | 6.5 |
| CVE-2022-41316 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA … | 2022-10-12 | 5.3 |
| CVE-2022-40716 | Hashicorp Consul: 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 … | 2022-09-23 | 6.5 |
| CVE-2022-40186 | Hashicorp Vault: An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine was found where, in a … | 2022-09-21 | 9.1 |
| CVE-2022-38149 | Hashicorp Consul Template: HashiCorp Consul Template up to 0.27.2, 0.28.2, and 0.29.1 may expose the contents of Vault secrets in the error returned by the … | 2022-08-17 | 7.5 |
| CVE-2022-36182 | Hashicorp Boundary: Hashicorp Boundary v0.8.0 is vulnerable to Clickjacking which allow for the interception of login credentials, re-direction of users to malicious … | 2022-10-27 | 6.1 |
| CVE-2022-36130 | Hashicorp Boundary: HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, … | 2022-09-01 | 9.9 |
| CVE-2022-36129 | Hashicorp Vault: HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that … | 2022-07-26 | 9.1 |
| CVE-2022-30689 | Hashicorp Vault: HashiCorp Vault and Vault Enterprise from 1.10.0 to 1.10.2 did not correctly configure and enforce MFA on login after server restarts. This affects … | 2022-05-17 | 5.3 |
| CVE-2022-30324 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise version 0.2.0 up to 1.3.0 were impacted by go-getter vulnerabilities enabling privilege escalation through the … | 2022-06-02 | 9.8 |
| CVE-2022-30323 | Hashicorp Go-getter: go-getter up to 1.5.11 and 2.0.2 panicked when processing password-protected ZIP files. Fixed in 1.6.1 and 2.1.0. | 2022-05-25 | 8.6 |
| CVE-2022-30322 | Hashicorp Go-getter: go-getter up to 1.5.11 and 2.0.2 allowed asymmetric resource exhaustion when go-getter processed malicious HTTP responses. Fixed in 1.6.1 and 2.1.0. | 2022-05-25 | 8.6 |
| CVE-2022-30321 | Hashicorp Go-getter: go-getter up to 1.5.11 and 2.0.2 allowed arbitrary host access via go-getter path traversal, symlink processing, and command injection flaws. Fixed … | 2022-05-25 | 8.6 |
| CVE-2022-29810 | Hashicorp Go-getter: The Hashicorp go-getter library before 1.5.11 does not redact an SSH key from a URL query parameter. | 2022-04-27 | 5.5 |
| CVE-2022-29153 | Hashicorp Consul: HashiCorp Consul and Consul Enterprise up to 1.9.16, 1.10.9, and 1.11.4 may allow server side request forgery when the Consul client agent follows … | 2022-04-19 | 7.5 |
| CVE-2022-26945 | Hashicorp Go-getter: go-getter up to 1.5.11 and 2.0.2 allowed protocol switching, endless redirect, and configuration bypass via abuse of custom HTTP response header … | 2022-05-25 | 9.8 |
| CVE-2022-25374 | Hashicorp Terraform Enterprise: HashiCorp Terraform Enterprise v202112-1, v202112-2, v202201-1, and v202201-2 were configured to log inbound HTTP requests in a manner that may … | 2022-02-25 | 7.5 |
| CVE-2022-25244 | Hashicorp Vault: Vault Enterprise clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration … | 2022-03-10 | 6.5 |
| CVE-2022-25243 | Hashicorp Vault: "Vault and Vault Enterprise 1.8.0 through 1.8.8, and 1.9.3 allowed the PKI secrets engine under certain configurations to issue wildcard … | 2022-03-10 | 6.5 |
| CVE-2022-24687 | Hashicorp Consul: 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 … | 2022-02-24 | 6.5 |
| CVE-2022-24686 | Hashicorp Nomad: HashiCorp Nomad and Nomad Enterprise 0.3.0 through 1.0.17, 1.1.11, and 1.2.5 artifact download functionality has a race condition such that the … | 2022-02-14 | 5.9 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.