HashiCorp Vault
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in HashiCorp Vault.
By the Year
In 2026 there have been 17 vulnerabilities in HashiCorp Vault with an average score of 6.3 out of ten. Last year, in 2025 Vault had 14 security vulnerabilities published. That is, 3 more vulnerabilities have already been reported in 2026 as compared to last year. Last year, the average CVE base score was greater by 1.39
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 17 | 6.29 |
| 2025 | 14 | 7.68 |
| 2024 | 10 | 6.71 |
| 2023 | 13 | 6.02 |
| 2022 | 6 | 6.97 |
| 2021 | 13 | 6.18 |
| 2020 | 11 | 7.01 |
| 2019 | 0 | 0.00 |
| 2018 | 1 | 8.10 |
It may take a day or so for new Vault 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 Vault Security Vulnerabilities
HashiCorp Vault <2.2.2 MFA login request expiration bypass
CVE-2026-92738
6.8 - Medium
- November 13, 2026
Vault'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.
Insufficient Session Expiration
HashiCorp Vault <2.2.2 ACL caseinsensitive user/group policy bypass
CVE-2026-128100
6.5 - Medium
- November 13, 2026
Vault 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.
Improper Handling of Case Sensitivity
HashiCorp Vault <2.2.2 Audit Log Prefix Injection (CVE-2026-93333)
CVE-2026-93333
2.7 - Low
- November 12, 2026
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.
Improper Output Neutralization for Logs
HashiCorp Vault <2.2.2 ACL slash bypass allows config delete
CVE-2026-93335
6.5 - Medium
- November 12, 2026
Vault 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.
Use of Non-Canonical URL Paths for Authorization Decisions
Vault <2.2.2 CE / <1.21.14 EE unauth cred leak via storage join
CVE-2026-92735
5.9 - Medium
- November 12, 2026
HashiCorp 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.
SSRF
Vault ACL Policy Bypass Allowing Privilege Escalation (Fix 2.1.2)
CVE-2026-89322
7.2 - High
- October 07, 2026
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.
Improper Handling of Case Sensitivity
HashiCorp Vault <1.21.12 ACL Policy Cache Traversal (CVE2026105820)
CVE-2026-105820
5.4 - Medium
- October 07, 2026
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.
Directory traversal
HashiCorp Vault <2.1.2 Plugin Dir RCE via Unvalidated Catalog Entries
CVE-2026-105816
8 - High
- October 07, 2026
Vault 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.
Directory traversal
HashiCorp Vault PKI ACME Unrestricted Identity Issue (pre-2.1.2)
CVE-2026-105818
5.9 - Medium
- October 07, 2026
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.
Insufficient Verification of Data Authenticity
Auth Bypass via Identity Path Manipulation in HashiCorp Vault 2.0.4
CVE-2026-5006
6.8 - Medium
- August 24, 2026
A 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.
Insecure Direct Object Reference / IDOR
Vault Enterprise NS Auth Bypass via Batch-Delete (pre-2.0.4/1.21.9)
CVE-2026-14886
8.2 - High
- August 10, 2026
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.
AuthZ
Vault ACL Engine ignores glob deny on LIST for trailing slash pre-2.0.3/1.21.8
CVE-2026-12624
4.3 - Medium
- August 10, 2026
Vaults 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.
AuthZ
HashiCorp Vault Audit Plugin Directory Protections Flaw (pre-2.0.1)
CVE-2026-5051
4.4 - Medium
- July 01, 2026
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.
Directory traversal
Vault 2.0.0 DoS: Unauth Root Token Gen/Rekey ops slot
CVE-2026-5807
7.5 - High
- April 17, 2026
Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate operators from completing these workflows. This vulnerability, CVE-2026-5807, is fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.
Allocation of Resources Without Limits or Throttling
Vault Auth Header Forwarding CVE-2026-4525 (v2.0.0,1.21.5,1.20.10,1.19.16)
CVE-2026-4525
7.5 - High
- April 17, 2026
If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
Insertion of Sensitive Information Into Sent Data
Vault ACME Validation Local-Target Disclosure (1.21.4, 2.0.0-)
CVE-2026-5052
5.3 - Medium
- April 17, 2026
Vaults PKI engines ACME validation did not reject local targets when issuing http-01 and tls-alpn-01 challenges. This may lead to these requests being sent to local network targets, potentially leading to information disclosure. Fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
SSRF
Vault Authenticated Deletion via Policy Globbing ( 2.0.0)
CVE-2026-3605
8.1 - High
- April 17, 2026
An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
Authentication Bypass Using an Alternate Path or Channel
Vault CE 1.21.0 / Enterprise 1.21.0: JSON DOS (unauthenticated)
CVE-2025-12044
7.5 - High
- October 23, 2025
Vault and Vault Enterprise (Vault) are vulnerable to an unauthenticated denial of service when processing JSON payloads. This occurs due to a regression from a previous fix for [+HCSEC-2025-24+|https://discuss.hashicorp.com/t/hcsec-2025-24-vault-denial-of-service-though-complex-json-payloads/76393] which allowed for processing JSON payloads before applying rate limits. This vulnerability, CVE-2025-12044, is fixed in Vault Community Edition 1.21.0 and Vault Enterprise 1.16.27, 1.19.11, 1.20.5, and 1.21.0.
Allocation of Resources Without Limits or Throttling
Vault AWS Auth Bypass (CVE-2025-11621) fixed 1.21.0/1.20.5/1.19.11/1.16.27
CVE-2025-11621
8.1 - High
- October 23, 2025
Vault and Vault Enterprises (Vault) AWS Auth method may be susceptible to authentication bypass if the role of the configured bound_principal_iam is the same across AWS accounts, or uses a wildcard. This vulnerability, CVE-2025-11621, is fixed in Vault Community Edition 1.21.0 and Vault Enterprise 1.21.0, 1.20.5, 1.19.11, and 1.16.27
Authentication Bypass Using an Alternate Path or Channel
Vault Memory Exhaustion via Large Payload (1.20.3+ Vulnerable)
CVE-2025-6203
7.5 - High
- August 28, 2025
A malicious user may submit a specially-crafted complex payload that otherwise meets the default request size limit which results in excessive memory and CPU consumption of Vault. This may lead to a timeout in Vaults auditing subroutine, potentially resulting in the Vault server to become unresponsive. This vulnerability, CVE-2025-6203, is fixed in Vault Community Edition 1.20.3 and Vault Enterprise 1.20.3, 1.19.9, 1.18.14, and 1.16.25.
Allocation of Resources Without Limits or Throttling
Vault LDAP MFA Bypass via username_as_alias; fixed in CE 1.20.2
CVE-2025-6013
- August 06, 2025
Vault and Vault Enterprises (Vault) ldap auth method may not have correctly enforced MFA if username_as_alias was set to true and a user had multiple CNs that are equal but with leading or trailing spaces. Fixed in Vault Community Edition 1.20.2 and Vault Enterprise 1.20.2, 1.19.8, 1.18.13, and 1.16.24.
TLS Cert Auth Issue in Vault 1.18.12-1.20.1
CVE-2025-6037
- August 01, 2025
Vault and Vault Enterprise (Vault) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault MFA Rate Limit Bypass & TOTP Reuse (CVE-2025-6015) before 1.20.1
CVE-2025-6015
- August 01, 2025
Vault and Vault Enterprises (Vault) login MFA rate limits could be bypassed and TOTP tokens could be reused. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault TOTP Engine Code Reuse Vulnerability (Replay) – Fixed 1.20.1
CVE-2025-6014
- August 01, 2025
Vault and Vault Enterprises (Vault) TOTP Secrets Engine code validation endpoint is susceptible to code reuse within its validity period. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault Privilege Escalation via Identity Endpoint (pre-1.20.0)
CVE-2025-5999
- August 01, 2025
A privileged Vault operator with write permissions to the root namespaces identity endpoint could escalate their own or another users token privileges to Vaults root policy. Fixed in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.6, 1.18.11 and 1.16.22.
Vault Privileged Operator RCE via Plugin Directory (before 1.20.1)
CVE-2025-6000
- August 01, 2025
A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a plugin directory is set in Vaults configuration. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault Userpass/LDAP Lockout Bypass before 1.20.1
CVE-2025-6004
- August 01, 2025
Vault and Vault Enterprises (Vault) user lockout feature could be bypassed for Userpass and LDAP authentication methods. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault Userpass Auth Timing Side Channel Username Enumeration
CVE-2025-6011
- August 01, 2025
A timing side channel in Vault and Vault Enterprises (Vault) userpass auth method allowed an attacker to distinguish between existing and non-existing users, and potentially enumerate valid usernames for Vaults Userpass auth method. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Vault DoS via Uncontrolled Cancellation in Rekey Ops Before 1.20.0
CVE-2025-4656
- June 25, 2025
Vault Community and Vault Enterprise rekey and recovery key operations can lead to a denial of service due to uncontrolled cancellation by a Vault operator. This vulnerability (CVE-2025-4656) has been remediated in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.6, 1.18.11, 1.17.17, and 1.16.22.
Vault Azure Auth Claims Validation Bypass (1.19.1+)
CVE-2025-3879
8.8 - High
- May 02, 2025
Vault Community, Vault Enterprise (Vault) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.
Vault KV Plugin v2 Log Exposure via Malformed API Payloads - Fixed in 1.19.3
CVE-2025-4166
6.5 - Medium
- May 02, 2025
Vault Community and Vault Enterprise Key/Value (kv) Version 2 plugin may unintentionally expose sensitive information in server and audit logs when users submit malformed payloads during secret creation or update operations via the Vault REST API. This vulnerability, identified as CVE-2025-4166, is fixed in Vault Community 1.19.3 and Vault Enterprise 1.19.3, 1.18.9, 1.17.16, 1.16.20.
Vault: DoS via Raft join API (before 1.18.1)
CVE-2024-8185
- October 31, 2024
Vault Community and Vault Enterprise (Vault) clusters using Vaults Integrated Storage backend are vulnerable to a denial-of-service (DoS) attack through memory exhaustion through a Raft cluster join API endpoint . An attacker may send a large volume of requests to the endpoint which may cause Vault to consume excessive system memory resources, potentially leading to a crash of the underlying system and the Vault process itself. This vulnerability, CVE-2024-8185, is fixed in Vault Community 1.18.1 and Vault Enterprise 1.18.1, 1.17.8, and 1.16.12.
Vault Priv Escalation via Root Namespace Identity Endpoint (Fixed 1.18.0)
CVE-2024-9180
7.2 - High
- October 10, 2024
A privileged Vault operator with write permissions to the root namespaces identity endpoint could escalate their own or another users privileges to Vaults root policy. Fixed in Vault Community Edition 1.18.0 and Vault Enterprise 1.18.0, 1.17.7, 1.16.11, and 1.15.16.
HashiCorp Vault SSH SE valid_principals flaw any host auth (pre-1.17.6)
CVE-2024-7594
8.8 - High
- September 26, 2024
Vaults SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vaults SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.
Vault 1.17.5/1.16.9 HMAC Audit Log Regression CVE-2024-8365
CVE-2024-8365
6.5 - Medium
- September 02, 2024
Vault Community Edition and Vault Enterprise experienced a regression where functionality that HMACd sensitive headers in the configured audit device, specifically client tokens and token accessors, was removed. This resulted in the plaintext values of client tokens and token accessors being stored in the audit log. This vulnerability, CVE-2024-8365, was fixed in Vault Community Edition and Vault Enterprise 1.17.5 and Vault Enterprise 1.16.9.
Insertion of Sensitive Information into Log File
Vault DoS via proxy_protocol_behavior deny_unauthorized before 1.17.2
CVE-2024-6468
- July 11, 2024
Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service. While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur. Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12.
Vault JWT Auth: Audience Claim Validation Bypass before 1.17.0
CVE-2024-5798
2.6 - Low
- June 12, 2024
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 may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing an invalid login to succeed when it should have been rejected. This vulnerability, CVE-2024-5798, was fixed in Vault and Vault Enterprise 1.17.0, 1.16.3, and 1.15.9
authentification
Vault Enterprise 1.15.8: Standby Audit Logs Sensitive HTTP Headers
CVE-2024-2877
5.5 - Medium
- April 30, 2024
Vault Enterprise, when configured with performance standby nodes and a configured audit device, will inadvertently log request headers on the standby node. These logs may have included sensitive HTTP request information in cleartext. This vulnerability, CVE-2024-2877, was fixed in Vault Enterprise 1.15.8.
Vault TLS Auth OCSP Validation Flaw v1.14.0-<1.16.0
CVE-2024-2660
6.8 - Medium
- April 04, 2024
Vault and Vault Enterprise TLS certificates auth method did not correctly validate OCSP responses when one or more OCSP sources were configured. This vulnerability, CVE-2024-2660, affects Vault and Vault Enterprise 1.14.0 and above, and is fixed in Vault 1.16.0 and Vault Enterprise 1.16.1, 1.15.7, and 1.14.11.
Vault TLS Cert Auth Bypass (1.15.5/1.14.10)
CVE-2024-2048
9.8 - Critical
- March 04, 2024
Vault and Vault Enterprise (Vault) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate. In this configuration, an attacker may be able to craft a malicious certificate that could be used to bypass authentication. Fixed in Vault 1.15.5 and 1.14.10.
Vault Log_RAW Audit Device May Expose Sensitive Data
CVE-2024-0831
6.5 - Medium
- February 01, 2024
Vault and Vault Enterprise (Vault) may expose sensitive information when enabling an audit device which specifies the `log_raw` option, which may log sensitive information to other audit devices, regardless of whether they are configured to use `log_raw`.
Insertion of Sensitive Information into Log File
Vault HTTP DoS via memory exhaustion 1.12.0+
CVE-2023-6337
7.5 - High
- December 08, 2023
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 large unauthenticated and authenticated HTTP requests from a client. Vault will attempt to map the request to memory, resulting in the exhaustion of available memory on the host, which may cause Vault to crash. Fixed in Vault 1.15.4, 1.14.8, 1.13.12.
Allocation of Resources Without Limits or Throttling
HashiCorp Vault memory exhaustion via policy check (DDoS) - before 1.15.2
CVE-2023-5954
7.5 - High
- November 09, 2023
HashiCorp Vault and Vault Enterprise inbound client requests triggering a policy check can lead to an unbounded consumption of memory. A large number of these requests may lead to denial-of-service. Fixed in Vault 1.15.2, 1.14.6, and 1.13.10.
Memory Leak
Vault Enterprise Sentinel Role Governing Policy DoS via CrossNamespace (1.14.4)
CVE-2023-3775
4.9 - Medium
- September 29, 2023
A Vault Enterprise Sentinel Role Governing Policy created by an operator to restrict access to resources in one namespace can be applied to requests outside in another non-descendant namespace, potentially resulting in denial of service. Fixed in Vault Enterprise 1.15.0, 1.14.4, 1.13.8.
Vault Google Cloud Secrets Engine Fails to Preserve IAM Conditions (pre-1.13.0)
CVE-2023-5077
7.5 - High
- September 29, 2023
The Vault and Vault Enterprise ("Vault") Google Cloud secrets engine did not preserve existing Google Cloud IAM Conditions upon creating or updating rolesets. Fixed in Vault 1.13.0.
Incorrect Permission Assignment for Critical Resource
CVE-2023-4680: HashiCorp Vault Transit Engine Nonce Bypass (1.61.14.3)
CVE-2023-4680
6.8 - Medium
- September 15, 2023
HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphertext and potentially derive the authentication subkey when using transit secrets engine without convergent encryption. Introduced in 1.6.0 and fixed in 1.14.3, 1.13.7, and 1.12.11.
Improper Input Validation
HashiCorp Vault LDAP Auth User Enumeration (pre1.14.1/1.13.5)
CVE-2023-3462
5.3 - Medium
- July 31, 2023
HashiCorp's Vault and Vault Enterprise are vulnerable to user enumeration when using the LDAP auth method. An attacker may submit requests of existent and non-existent LDAP users and observe the response from Vault to check if the account is valid on the LDAP server. This vulnerability is fixed in Vault 1.14.1 and 1.13.5.
Side Channel Attack
Vault Enterprise Namespace Crash <1.14.1 (CVE20233774)
CVE-2023-3774
4.9 - Medium
- July 28, 2023
An unhandled error in Vault Enterprise's namespace creation may cause the Vault process to crash, potentially resulting in denial of service. Fixed in 1.14.1, 1.13.5, and 1.12.9.
Improper Handling of Exceptional Conditions
Vault KV-v2 Diff Viewer HTML Injection before 1.14.0 (CVE-2023-2121)
CVE-2023-2121
5.4 - Medium
- June 09, 2023
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 vulnerability, CVE-2023-2121, is fixed in Vault 1.14.0, 1.13.3, 1.12.7, and 1.11.11.
XSS
Vault Enterprise <=1.13.1: HSM Padding Oracle on CKM_AES_CBC_PAD/CBC Attack
CVE-2023-2197
2.5 - Low
- May 01, 2023
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 or CKM_AES_CBC encryption mechanisms. An attacker with privileges to modify storage and restart Vault may be able to intercept or modify cipher text in order to derive Vaults root key. Fixed in 1.13.2
Inadequate Encryption Strength
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for HashiCorp Vault or by HashiCorp? Click the Watch button to subscribe.