Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,384
Published in 7 days
1,885
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “HashiCorp Vault”

83 vulnerabilities
  1. High 7.7

    CVE-2026-133094 · TeamCity

    In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secrets

    Published 19 Nov 2026 · Fixed in 2026.2.2 · CVE Program
  2. Medium 6.8

    CVE-2026-92738 · HashiCorp Vault

    Expired Vault login MFA requests may remain redeemable

    Published 13 Nov 2026 · Fixed in 2.2.2 · CVE Program
  3. Medium 6.5

    CVE-2026-128100 · HashiCorp Vault

    Vault vulnerable to ACL deny bypass via case-variant auth method user and group names

    Published 13 Nov 2026 · Fixed in 2.2.2 · CVE Program
  4. Low 2.7

    CVE-2026-93333 · HashiCorp Vault

    Vault audit device prefix vulnerable to log injection

    Published 12 Nov 2026 · Fixed in 2.2.2 · CVE Program
  5. Medium 6.5

    CVE-2026-93335 · HashiCorp Vault

    Vault vulnerable to ACL deny bypass via trailing slash

    Published 12 Nov 2026 · Fixed in 2.2.2 · CVE Program
  6. Medium 5.9

    CVE-2026-92735 · HashiCorp Vault

    Vault integrated storage join may disclose server environment credentials

    Published 12 Nov 2026 · Fixed in 2.2.2 · CVE Program
  7. High 7.2

    CVE-2026-89322 · HashiCorp Vault

    Vault ACL Policy Evaluation May Allow Bypass of Deny Restrictions

    Published 7 Oct 2026 · Fixed in 2.1.2 · CVE Program
  8. Medium 5.4

    CVE-2026-105820 · HashiCorp Vault

    Vault ACL Policy Cache Vulnerable to Cross-Namespace Policy Resolution

    Published 7 Oct 2026 · Fixed in 2.1.2 · CVE Program
  9. High 8.0

    CVE-2026-105816 · HashiCorp Vault

    Vault Vulnerable to Arbitrary Code Execution via Plugin Catalog Entries Restored From Raft Snapshots

    Published 7 Oct 2026 · Fixed in 2.1.2 · CVE Program
  10. Medium 5.9

    CVE-2026-105818 · HashiCorp Vault

    Vault PKI ACME Issues Certificate With Unvalidated SANs

    Published 7 Oct 2026 · Fixed in 2.1.2 · CVE Program
  11. High 7.5

    CVE-2026-5807 · HashiCorp Vault

    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.

    Published 17 Apr 2026 · Fixed in 2.0.0 · NVD
  12. High 8.6

    CVE-2026-5052 · HashiCorp Vault

    Vault’s PKI engine’s 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.

    Published 17 Apr 2026 · Fixed in 1.20.10, 1.21.5, 2.0.0 · NVD
  13. High 8.8

    CVE-2026-4525 · HashiCorp Vault

    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.

    Published 17 Apr 2026 · Fixed in 1.20.10, 1.21.5, 2.0.0 · NVD
  14. High 8.1

    CVE-2026-3605 · HashiCorp Vault

    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.

    Published 17 Apr 2026 · Fixed in 1.20.10, 1.21.5, 2.0.0 · NVD
  15. High 7.5

    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 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,…

    Published 23 Oct 2025 · Fixed in 1.16.27, 1.20.5, 1.21.0 · NVD
  16. High 8.1

    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 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

    Published 23 Oct 2025 · Fixed in 1.19.11, 1.20.5, 1.21.0 · NVD
  17. High 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 memory and CPU consumption of Vault. This may lead to a timeout in Vault’s 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…

    Published 28 Aug 2025 · Fixed in 1.19.11, 1.20.5, 1.21.0 · NVD
  18. High 8.1

    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 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.

    Published 6 Aug 2025 · Fixed in 1.18.13, 1.19.8, 1.20.2 · NVD
  19. Medium 6.8

    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 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…

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  20. Medium 5.7

    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 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  21. Medium 6.5

    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 in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  22. Low 3.7

    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 non-existing users, and potentially enumerate valid usernames for Vault’s 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.

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  23. Medium 5.3

    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 Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  24. Critical 9.1

    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 plugin directory is set in Vault’s 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.

    Published 1 Aug 2025 · Fixed in 1.18.12, 1.19.7, 1.20.1 · NVD
  25. High 7.2

    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 privileges to Vault’s 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.

    Published 1 Aug 2025 · Fixed in 1.18.11, 1.19.6, 1.20.0 · NVD
  26. Low 3.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 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.

    Published 25 Jun 2025 · Fixed in 1.18.11, 1.19.6, 1.20.0 · NVD
  27. High 8.8

    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 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.

    Published 2 May 2025 · Fixed in 1.17.14, 1.18.7, 1.19.1 · NVD
  28. Medium 6.5

    CVE-2025-4166 · HashiCorp Vault, OpenBao

    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.

    Published 2 May 2025 · Fixed in 1.18.9, 1.19.3, 2.2.2 · NVD
  29. High 7.5

    CVE-2024-8185 · HashiCorp Vault, OpenBao

    Vault Community and Vault Enterprise (“Vault”) clusters using Vault’s 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…

    Published 31 Oct 2024 · Fixed in 1.17.8, 1.18.1, 2.0.3 · NVD
  30. High 7.2

    CVE-2024-9180 · HashiCorp Vault, OpenBao

    A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s privileges to Vault’s 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.

    Published 10 Oct 2024 · Fixed in 1.16.11, 1.18.0, 2.0.3 · NVD
  31. High 8.8

    CVE-2024-7594 · HashiCorp Vault, OpenBao

    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 of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s 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…

    Published 26 Sept 2024 · Fixed in 1.16.10, 1.17.6, 2.0.2 · NVD
  32. Medium 6.5

    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 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…

    Published 2 Sept 2024 · Fixed in 1.16.9, 1.17.5 · NVD
  33. Medium 5.4

    CVE-2024-43808 · TeamCity

    In JetBrains TeamCity before 2024.07.1 self XSS was possible in the HashiCorp Vault plugin

    Published 16 Aug 2024 · Fixed in 2024.07.1 · NVD
  34. High 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, 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…

    Published 11 Jul 2024 · Fixed in 1.15.12, 1.16.6, 1.17.2 · NVD
  35. High 7.5

    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 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,…

    Published 12 Jun 2024 · Fixed in 1.15.9, 1.16.3 · NVD
  36. Medium 5.5

    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 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.

    Published 30 Apr 2024 · Fixed in 1.15.8 · NVD
  37. Medium 6.8

    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. 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.

    Published 4 Apr 2024 · Fixed in 1.14.11, 1.15.7, 1.16.0 · NVD
  38. Critical 9.8

    CVE-2024-2048 · HashiCorp Vault, OpenBao

    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.

    Published 4 Mar 2024 · Fixed in 1.14.10, 1.15.5, 2.0.0 · NVD
  39. Medium 6.5

    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 log sensitive information to other audit devices, regardless of whether they are configured to use `log_raw`.

    Published 1 Feb 2024 · Fixed in 1.15.5 · NVD
  40. High 7.5

    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 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.

    Published 8 Dec 2023 · Fixed in 1.13.12, 1.14.8, 1.15.4 · NVD
  41. High 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 number of these requests may lead to denial-of-service. Fixed in Vault 1.15.2, 1.14.6, and 1.13.10.

    Published 9 Nov 2023 · Fixed in 1.13.10, 1.14.6, 1.15.2 · NVD
  42. High 7.5

    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 updating rolesets. Fixed in Vault 1.13.0.

    Published 29 Sept 2023 · Fixed in 1.13.0 · NVD
  43. Medium 4.9

    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 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.

    Published 29 Sept 2023 · Fixed in 1.13.8, 1.14.4 · NVD
  44. Medium 6.8

    CVE-2023-4680 · HashiCorp Vault

    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…

    Published 15 Sept 2023 · Fixed in 1.12.11, 1.13.7, 1.14.3 · NVD
  45. Medium 5.3

    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 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.

    Published 31 Jul 2023 · Fixed in 1.13.5 · NVD
  46. Medium 4.9

    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 in 1.14.1, 1.13.5, and 1.12.9.

    Published 28 Jul 2023 · NVD
  47. Medium 5.4

    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 vulnerability, CVE-2023-2121, is fixed in Vault 1.14.0, 1.13.3, 1.12.7, and 1.11.11.

    Published 9 Jun 2023 · Fixed in 1.11.11, 1.12.7, 1.13.3 · NVD
  48. Low 2.5

    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 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 Vault’s root key. Fixed in 1.13.2

    Published 1 May 2023 · Fixed in 1.13.2 · NVD
  49. Medium 4.7

    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 with access to, and the ability to observe a large number of unseal operations on the host through a side channel may reduce the search space of a brute force effort to recover the Shamir shares. Fixed in Vault 1.13.1, 1.12.5, and 1.11.9.

    Published 30 Mar 2023 · Fixed in 1.11.9, 1.12.5, 1.13.1 · NVD
  50. Medium 6.5

    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 resulting in denial of service of the PKI mount. This bug did not affect public or private key material, trust chains or certificate issuance. Fixed in Vault 1.13.1, 1.12.5, and 1.11.9.

    Published 30 Mar 2023 · Fixed in 1.11.9, 1.12.5, 1.13.1 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.