HashiCorp
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any HashiCorp product.
RSS Feeds for HashiCorp security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in HashiCorp products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by HashiCorp Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 60 vulnerabilities in HashiCorp with an average score of 6.8 out of ten. Last year, in 2025 HashiCorp had 23 security vulnerabilities published. That is, 37 more vulnerabilities have already been reported in 2026 as compared to last year. Last year, the average CVE base score was greater by 0.29
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 60 | 6.78 |
| 2025 | 23 | 7.07 |
| 2024 | 24 | 6.38 |
| 2023 | 30 | 6.44 |
| 2022 | 31 | 7.16 |
| 2021 | 32 | 7.07 |
| 2020 | 27 | 7.40 |
| 2019 | 5 | 0.00 |
| 2018 | 4 | 7.28 |
It may take a day or so for new HashiCorp vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent HashiCorp Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-19194 | Nov 13, 2026 |
HashiCorp cap JWT validation bypass (pre0.14.0)The HashiCorp cap JWT validation library before version 0.14.0 is vulnerable to a claims validation bypass that may cause downstream applications to make authorization decisions using claim values different from those validated. Exploitation requires attacker-controlled claims in a JWT signed by a key trusted by the application. This vulnerability (CVE-2026-19194) is fixed in cap 0.14.0. |
|
| CVE-2026-92738 | Nov 13, 2026 |
HashiCorp Vault <2.2.2 MFA login request expiration bypassVault's Login MFA feature did not consistently enforce the lifetime of pending two-phase login requests. This may allow a user who previously completed the first authentication factor to complete MFA and obtain a Vault token after the pending request should have expired, including after the user's primary credential has been rotated. This vulnerability (CVE-2026-92738) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.26. |
|
| CVE-2026-128100 | Nov 13, 2026 |
HashiCorp Vault <2.2.2 ACL caseinsensitive user/group policy bypassVault Community Edition and Vault Enterprise did not apply explicit ACL policy deny rules to letter case variants of user and group names in auth methods that treat these names as case-insensitive. This may allow an authenticated user with delegated permissions to modify a protected user or group, potentially leading to privilege escalation. This vulnerability (CVE-2026-128100) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25. |
|
| CVE-2026-93333 | Nov 12, 2026 |
HashiCorp Vault <2.2.2 Audit Log Prefix Injection (CVE-2026-93333)Vault's audit devices did not validate the contents of a configured audit log prefix and did not consistently enforce the server-level setting that restricts audit log prefixing. This may allow a privileged operator to inject content into audit logs, potentially leading to forged or misleading audit records. This vulnerability (CVE-2026-93333) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25. |
|
| CVE-2026-93335 | Nov 12, 2026 |
HashiCorp Vault <2.2.2 ACL slash bypass allows config deleteVault Community Edition and Vault Enterprise did not consistently apply explicit ACL policy deny rules to request paths that differ only by a trailing slash. This may allow an authenticated user who holds a broader delete permission on system configuration paths to disable a secrets engine, auth method, or audit device that a more specific deny rule was intended to protect. This vulnerability (CVE-2026-93335) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25. |
|
| CVE-2026-92735 | Nov 12, 2026 |
Vault <2.2.2 CE / <1.21.14 EE unauth cred leak via storage joinHashiCorp Vault and Vault Enterprise are vulnerable to an issue in the integrated storage join process that may allow an unauthenticated attacker with network access to a new, uninitialized node to cause that node to send credentials from its server environment to an attacker-controlled server. This vulnerability (CVE-2026-92735) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25. |
|
| CVE-2026-13303 | Oct 29, 2026 |
Boundary SSRF in Vault Credential Store (v<1.0.2, <0.21.6)HashiCorp Boundary and Boundary Enterprise are vulnerable to a server-side request forgery in the Vault credential store integration that may allow an authenticated user with permission to manage credential stores and credential libraries within a project to cause the Boundary controller to issue outbound requests to a network destination of the requester's choosing and to receive the response. This may expose endpoints reachable only from the controller's host, such as a cloud instance metadata service. This vulnerability, CVE-2026-13303, is fixed in Boundary Enterprise 1.0.2 and 0.21.6. |
|
| CVE-2026-119168 | Oct 29, 2026 |
HashiCorp Nomad symlink follow bug allows host privilege escalation (pre2.1.1)HashiCorp Nomad and Nomad Enterprise are vulnerable to symlink following during same-client allocation data migration that may allow a malicious workload to change permissions and ownership of host directories. This could allow unauthorized access to host data or modification of host files, potentially leading to privilege escalation. This vulnerability (CVE-2026-119168) is fixed in Nomad 2.1.1 and Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18. |
|
| CVE-2026-105626 | Oct 26, 2026 |
HashiCorp Consul HTTP API DoS (pre2.1.0 / 1.21.18)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 2.1.0 and 1.21.19. |
|
| CVE-2026-105608 | Oct 26, 2026 |
HashiCorp Consul Service Mesh Proxy Auth Bypass (pre2.1.0)HashiCorp Consul and Consul Enterprise are vulnerable to an authorization bypass in service mesh proxy registration. This may allow a user with service write permission to apply Envoy escape-hatch configuration without the required mesh write permission. This vulnerability (CVE-2026-105608) is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19. |
|
| CVE-2026-105765 | Oct 26, 2026 |
Consul Agent LEAF Cert API Auth Bypass Allow Private Key Leak (1.17.0-2.1.0)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 vulnerability (CVE-2026-105765) is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19. |
|
| CVE-2026-19585 | Oct 08, 2026 |
Path Traversal in HashiCorp go-getter before 1.8.10 / v2 2.2.5HashiCorp go-getter versions before 1.8.10 and go-getter/v2 versions before 2.2.5 are vulnerable to path traversal during S3 and GCS directory downloads, which may allow files to be written outside the requested destination. This vulnerability (CVE-2026-19585) is fixed in go-getter 1.8.10 and go-getter/v2 2.2.5. |
|
| CVE-2026-89322 | Oct 07, 2026 |
Vault ACL Policy Bypass Allowing Privilege Escalation (Fix 2.1.2)Vault and Vault Enterprise did not consistently evaluate ACL policies against the canonical form of resource and policy names. This may allow an authenticated user with delegated permissions to bypass an explicit deny restriction and access a protected resource or assign a denied policy, potentially leading to privilege escalation. This vulnerability (CVE-2026-89322) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. |
|
| CVE-2026-105820 | Oct 07, 2026 |
HashiCorp Vault <1.21.12 ACL Policy Cache Traversal (CVE2026105820)Vault's ACL policy cache allowed namespace traversal when policy names contained path traversal constructs. This may allow a token assigned specially crafted policy names to use the capabilities of policies defined in other namespaces, including the root namespace. This vulnerability (CVE-2026-105820) is fixed in Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. Vault Community Edition does not support namespaces, and is not affected. |
|
| CVE-2026-105816 | Oct 07, 2026 |
HashiCorp Vault <2.1.2 Plugin Dir RCE via Unvalidated Catalog EntriesVault and Vault Enterprise did not consistently verify that stored plugin catalog entries reference binaries within the configured plugin directory. When Vault uses Shamir seals and has an external plugin directory configured, a privileged operator able to restore an Integrated Storage (Raft) snapshot may be able to execute arbitrary code on the Vault host. This vulnerability (CVE-2026-105816) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. |
|
| CVE-2026-105818 | Oct 07, 2026 |
HashiCorp Vault PKI ACME Unrestricted Identity Issue (pre-2.1.2)Vault's PKI secrets engine ACME server did not restrict certificate identities that ACME challenges do not validate when issuing certificates under the default directory policy. This may allow an ACME client to obtain a certificate containing unverified identity claims, potentially enabling impersonation toward systems that trust certificates issued by the affected Vault PKI mount. This vulnerability (CVE-2026-105818) is fixed in Vault Community Edition 2.1.2, and Vault Enterprise 2.1.2, 1.21.12, 1.20.17, and 1.19.23. |
|
| CVE-2026-88922 | Sep 15, 2026 |
go-getter PrivEsc via Archive Decompress (<=1.8.8/2.2.3)The go-getter library up to versions 1.8.8 and 2.2.3 is vulnerable to a privilege escalation issue in its archive decompression handling that may allow a crafted archive to cause extracted files to be created with elevated permission bits. Where extraction is performed by a privileged user, this may allow a local actor to obtain the privileges of the extracting process. This vulnerability (CVE-2026-88922) is fixed in go-getter 1.8.9 and 2.2.4. |
|
| CVE-2026-87993 | Sep 10, 2026 |
Consul-Template 0.43.0: Prevent Vault Secrets Leak via Error HandlingThe consul-template library is vulnerable to an information disclosure issue in its error handling path that may allow Vault secret values to appear in template error messages, log output, and downstream surfaces such as Nomad task events. This vulnerability (CVE-2026-87993) is fixed in consul-template 0.43.0. |
|
| CVE-2026-88021 | Sep 10, 2026 |
Consul Auth Bypass in Connect Mesh via Unescaped Service Names (2.0.3)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 certain characters in service names, namespaces, and partitions, causing the generated authorization rules to match more broadly than intended. This vulnerability (CVE-2026-88021) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4. |
|
| CVE-2026-87107 | Sep 10, 2026 |
Consul Auth Bypass: Catalog Dereg Path (2.0.3) Deletes PeerImported ObjectsConsul and Consul Enterprise are vulnerable to an authorization bypass in the catalog deregistration path that may allow a local ACL token to delete peer-imported catalog objects. 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. 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. |
|
| CVE-2026-87106 | Sep 10, 2026 |
Consul RPC Listener DoS via auth mem exhaustion pre-2.0.4Consul 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 without holding a valid ACL token. This vulnerability (CVE-2026-87106) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4. |
|
| CVE-2026-87090 | Sep 10, 2026 |
Consul Auth Bypass in Catalog Node-Write Path (2.0.3)Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog node-write path that may allow an authenticated attacker to delete another node's catalog registration and take over its node identity. An attacker with a token granting node-write permission on any single node name may exploit this issue if they can obtain the node ID of a node they do not control. This vulnerability (CVE-2026-87090) is fixed in Consul 2.0.4 and Consul Enterprise 1.21.18, 1.22.12 and 2.0.4. |
|
| CVE-2026-5006 | Aug 24, 2026 |
Auth Bypass via Identity Path Manipulation in HashiCorp Vault 2.0.4A vulnerability was identified in HashiCorp Vault and Vault Enterprise (Vault) such that an authenticated attacker may manipulate an identity value referenced by a templated policy path to gain unintended access to Vault paths. An attacker who can control the referenced identity value may include slash ({{/}}) characters that Vault interprets as additional path segments when rendering the policy. This vulnerability, CVE-2026-5006, was fixed in Vault Community Edition 2.0.4 and Vault Enterprise 2.0.4, 1.21.9, 1.20.14, and 1.19.20. |
|
| CVE-2026-14978 | Aug 19, 2026 |
HashiCorp go-slug 0.4.00.18.2 Unicode Normalization .terraformignore BypassHashiCorp go-slug 0.4.0 through 0.18.2 could allow a local attacker to bypass .terraformignore exclusions and cause sensitive files to be included in Terraform slug uploads due to improper handling of Unicode normalization during path matching. |
|
| CVE-2026-19589 | Aug 17, 2026 |
Packer <=1.15.4 Plugin Installer FS Modification CVE-2026-19589Packer up to 1.15.4 is vulnerable to an issue in the third-party plugin installer that may allow unintended file system modification and could lead to code execution. A user who installs a plugin from a malicious or compromised source may be affected. This vulnerability (CVE-2026-19589) is fixed in Packer 1.16.0. |
|
| CVE-2026-8715 | Aug 13, 2026 |
Vault Secrets Op 1.3.0-1.4.1: AppRole Auth Enables File Read & Credential LeakVault Secrets Operator 1.3.0 up to 1.4.1 is vulnerable to an arbitrary file read and credential exfiltration issue in the AppRole authentication configuration that may allow a tenant with limited Kubernetes RBAC permissions to read files from the operator pod's filesystem and transmit their contents to a tenant-controlled endpoint, potentially leading to privilege escalation within the cluster. This vulnerability (CVE-2026-8715) is fixed in Vault Secrets Operator 1.5.0. |
|
| CVE-2026-14886 | Aug 10, 2026 |
Vault Enterprise NS Auth Bypass via Batch-Delete (pre-2.0.4/1.21.9)Vault Enterprise's identity entity batch-delete endpoint is vulnerable to a cross-namespace authorization bypass that may allow an authenticated caller in one namespace to permanently delete the storage backing of entities belonging to another namespace. This vulnerability (CVE-2026-14886) is fixed in Vault Enterprise 2.0.4, 1.21.9, 1.20.14 and 1.19.20. |
|
| CVE-2026-12624 | Aug 10, 2026 |
Vault ACL Engine ignores glob deny on LIST for trailing slash pre-2.0.3/1.21.8Vaults ACL policy engine did not consistently enforce a wildcard (glob) deny rule against LIST requests made with a trailing slash on the denied path. This may allow a token holding a broader allow rule alongside a narrower wildcard deny rule to enumerate the names of entries beneath a path it was intended to be denied access to. This vulnerability (CVE-2026-12624) is fixed in Vault Community Edition 2.0.3 and Vault Enterprise 2.0.3, 1.21.8, 1.20.13, and 1.19.19. |
|
| CVE-2026-19113 | Aug 07, 2026 |
Consul HTTP API Excess Memory: Unauth DoS 1.3.0-2.0.2Consul Community Edition and Consul Enterprise 1.3.0 through 2.0.2 are vulnerable to an unauthenticated denial of service in several agent HTTP API endpoints. A remote caller could cause the agent to consume substantial memory before the request was rejected. This vulnerability, CVE-2026-19113, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-15972 | Aug 07, 2026 |
Consul 1.13.0-2.0.2 Unauthenticated DoS via Unbounded gRPC ListenerConsul Community Edition and Consul Enterprise 1.13.0 through 2.0.2 are vulnerable to an unauthenticated denial of service through unbounded connection acceptance on the external gRPC listeners. A remote attacker may exhaust agent file descriptors, goroutines, and memory by opening many incomplete connections, potentially preventing legitimate clients from connecting. This vulnerability, CVE-2026-15972, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-15970 | Aug 07, 2026 |
Consul L7 Intent Auth Bypass via Custom Public Listener (<=2.0.2)Consul Community Edition and Consul Enterprise 1.20.1 through 2.0.2 are vulnerable to an L7 intention authorization bypass when a service proxy is configured with a custom public listener. An authenticated mesh workload may reach HTTP paths that are blocked by a path-based deny intention. This vulnerability, CVE-2026-15970, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-19017 | Aug 07, 2026 |
Consul CE/Ent 1.18.21-2.0.2 Partial File Read via Vault CA JWT/AppRoleConsul 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 to read and forward credential files outside the intended scope, potentially leading to the exfiltration of sensitive secrets from the Consul server host. This vulnerability, CVE-2026-19017, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-19015 | Aug 07, 2026 |
Unbounded Cache Growth in Consul Connect CA Roots (1.2.02.0.2)Consul Community Edition and Consul Enterprise 1.2.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect CA roots endpoint that may allow a remote caller to grow the agent's Connect CA roots cache without bound, defeating the operator's cache-disable configuration. This vulnerability, CVE-2026-19015, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-19014 | Aug 07, 2026 |
Uncontrolled Resource Consumption in Consul Connect Auth Endpt 1.17-2.0.2Consul Community Edition and Consul Enterprise 1.17.0 through 2.0.2 are vulnerable to an uncontrolled resource consumption issue in the Connect authorization endpoint that may allow a caller to grow the agent's intention-match cache without bound, defeating the operator's cache-disable configuration. This vulnerability, CVE-2026-190124, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-19012 | Aug 07, 2026 |
Consul Auth-DOS: service-router config downgrade crashConsul Community Edition and Consul Enterprise 1.18.0 through 2.0.2 are vulnerable to an authenticated denial of service in the Enterprise-to-Community Edition downgrade path that may allow an authorized caller to crash the Consul server. A caller with config-entry write permission can submit a service-router configuration entry that causes the agent to exit unexpectedly. This vulnerability, CVE-2026-19012, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-19016 | Aug 07, 2026 |
Consul txAPI Session Delete ACL Flaw v1.19.12.0.2Consul Community Edition and Consul Enterprise 1.19.1 through 2.0.2 did not enforce the {{session:write}} ACL permission for session deletion operations submitted through the transaction API. An authenticated caller with network access to the Consul server RPC port could delete arbitrary sessions without holding the required permission. This vulnerability, CVE-2026-19016, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3. |
|
| CVE-2026-16326 | Jul 29, 2026 |
Session State Leak in consul-mcp-server 0.1.0-0.1.3 (CVE-2026-16326)In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not properly isolate session state in stateless mode, which may allow one client's Consul authentication token to be used for subsequent requests from other clients. This vulnerability (CVE-2026-16326) is fixed in consul-mcp-server 0.1.4. |
|
| CVE-2026-16328 | Jul 29, 2026 |
consul-mcp-server 0.1.0-3 Header Injection Allows Redirect to Consul APIIn consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an attacker-controlled endpoint, potentially exfiltrating the Consul token configured on the server. This vulnerability, CVE-2026-16328, is fixed in consul-mcp-server 0.1.4. |
|
| CVE-2026-16498 | Jul 28, 2026 |
Terraform-MCP-Server <1.1.0: Cross-Tenant Credential Reuse via Streamable-HTTPThe terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that may allow one user's Terraform token to be used to execute tool calls on behalf of subsequent users. This vulnerability, CVE-2026-16498, is fixed in terraform-mcp-server 1.1.0. |
|
| CVE-2026-16496 | Jul 28, 2026 |
terraform-mcp-server v1.1.0 Auth Bypass in Streamable-HTTP ModeThe terraform-mcp-server before version 1.1.0 is vulnerable to an authorization bypass in the streamable-HTTP stateful transport mode that may allow a user who obtains another user's MCP session ID to have their tool calls executed using that user's Terraform credentials. This vulnerability, CVE-2026-16496, is fixed in terraform-mcp-server 1.1.0. |
|
| CVE-2026-14869 | Jul 28, 2026 |
terraform-mcp-server SSRF in streamable-HTTP before 1.1.0The terraform-mcp-server before version 1.1.0 is vulnerable to a server-side request forgery issue in the streamable-HTTP transport that may allow an unauthenticated remote client to redirect the server's Terraform API requests, and the server-side authorization token, to an attacker-controlled endpoint. This vulnerability, CVE-2026-14869, is fixed in terraform-mcp-server 1.1.0. |
|
| CVE-2026-14896 | Jul 08, 2026 |
Nomad 2.0.4/1.11.8/1.10.14: CrossNS Auth Bypass in Host VolumesHashiCorp Nomad and Nomad Enterprise are vulnerable to a cross-namespace authorization bypass in the dynamic host volumes feature that may allow an operator holding the host volume delete permission in one namespace to delete a sticky volume claim belonging to a job in another namespace. This vulnerability, CVE-2026-14896, is fixed in Nomad Community Edition 2.0.4 and Nomad Enterprise 2.0.4, 1.11.8, and 1.10.14. |
|
| CVE-2026-14361 | Jul 08, 2026 |
consultemplate 0.42.1: Path Redirection in writeToFile (CVE2026-14361)The consul-template library before version 0.42.1 is vulnerable to a path redirection issue in the writeToFile template helper that may allow template output to be written outside the intended directory or to overwrite an existing file. This vulnerability (CVE-2026-14361) is fixed in consul-template 0.42.1. |
|
| CVE-2026-14891 | Jul 08, 2026 |
Nomad Docker Driver Sandbox Escape via Unauthorized Bind-Mount Before 2.0.4HashiCorp Nomad and Nomad Enterprise are vulnerable to a sandbox escape in the Docker task driver that may allow a job submitter to bind-mount a host path into a container even when volume bind mounts are disabled, potentially leading to reading and writing files on the host. This vulnerability, CVE-2026-14891, is fixed in Nomad Community Edition 2.0.4 and Nomad Enterprise 2.0.4, 1.11.8, and 1.10.14. |
|
| CVE-2026-14373 | Jul 08, 2026 |
HashiCorp Nomad: allow_privileged Not Enforced (pre 2.0.4/1.11.8/1.10.14)HashiCorp Nomad and Nomad Enterprise did not enforce the allow_privileged restriction for the Docker task driver's host namespace mode options. This may allow an authenticated job submitter to run a container in a host namespace and access information belonging to the host or to other workloads on the same client. This vulnerability, CVE-2026-14373, is fixed in Nomad Community Edition 2.0.4 and Nomad Enterprise 2.0.4, 1.11.8, and 1.10.14. |
|
| CVE-2026-14362 | Jul 08, 2026 |
HashiCorp memberlist <0.6.0 DoS via Push/Pull Gossip PortHashiCorp memberlist before version 0.6.0 is vulnerable to a denial-of-service issue in its push/pull state handling that may allow an attacker with network access to the gossip port to exhaust memory on a receiving node and cause the process to terminate. This vulnerability (CVE-2026-14362) is fixed in memberlist 0.6.0. |
|
| CVE-2026-14468 | Jul 06, 2026 |
Terraform Enterprise VCS Module Ingestion Path Traversal (CVE-2026-14468)HashiCorp Terraform Enterprise contained an issue in its version control system (VCS) ingestion of registry modules that did not correctly enforce the intended boundary on packaged module content. This may allow an authenticated user to include files from outside the intended repository content in a module and then download them, potentially exposing sensitive files readable by the ingestion process. This vulnerability, CVE-2026-14468, is fixed in Terraform Enterprise v2.0.4 and v1.2.4. |
|
| CVE-2026-5051 | Jul 01, 2026 |
HashiCorp Vault Audit Plugin Directory Protections Flaw (pre-2.0.1)HashiCorp Vault and Vault Enterprise prior to 2.0.1 audit device validation logic did not consistently apply plugin directory protections when the legacy file audit path option was used. This vulnerability (CVE-2026-5051) is fixed in 2.0.1, 1.21.6, 1.20.11, and 1.19.17. |
|
| CVE-2026-7474 | May 12, 2026 |
Nomad Path Traversal CVE-2026-7474, Code Exec via Client Host, fixed in 2.0.1HashiCorp Nomad and Nomad Enterprise prior to 2.0.1 are vulnerable to code execution on the client host through a path traversal attack. This vulnerability (CVE-2026-7474) is fixed in Nomad 2.0.1, 1.11.5 and 1.10.11. |
|
| CVE-2026-8052 | May 12, 2026 |
Nomad Exec2 Driver <0.1.2 Arbitrary File Read/Write via Symlink (CVE-2026-8052)HashiCorp Nomads exec2 task driver prior to 0.1.2 is vulnerable to arbitrary file read and write on the client host as the Nomad process user through a symlink attack. This vulnerability (CVE-2026-8052) is fixed in version 0.1.2 of the exec2 task driver. |