{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "HashiCorp Vault Enterprise: all CVE events",
 "home_page_url": "https://patchwire.jonathanross.dev/products/hashicorp--vault-enterprise/",
 "feed_url": "https://patchwire.jonathanross.dev/feeds/products/hashicorp--vault-enterprise/all.json",
 "authors": [
  {
   "name": "Patchwire"
  }
 ],
 "language": "en",
 "items": [
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-89322/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-89322/",
   "title": "CVE-2026-89322 · HashiCorp Vault · disclosed",
   "content_text": "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.",
   "date_published": "2026-10-07T22:01:37Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-105820/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-105820/",
   "title": "CVE-2026-105820 · HashiCorp Vault Enterprise · disclosed",
   "content_text": "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.",
   "date_published": "2026-10-07T21:48:08Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-105816/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-105816/",
   "title": "CVE-2026-105816 · HashiCorp Vault · disclosed",
   "content_text": "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.",
   "date_published": "2026-10-07T21:37:03Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-105818/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-105818/",
   "title": "CVE-2026-105818 · HashiCorp Vault · disclosed",
   "content_text": "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.",
   "date_published": "2026-10-07T21:21:05Z"
  }
 ]
}
