Vault PKI ACME Issues Certificate With Unvalidated SANs

published 2026-10-07 32 d ago modified 2026-10-16 23 d ago also BIT-vault-2026-105818 , EUVD-2026-94641

cvss: 5.9; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits: 0; none known

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.

Patch / fix

fixed in 3

bitnami vault 2.1.2
HashiCorp Vault 2.1.2
HashiCorp Vault Enterprise 1.19.23, 1.20.17, 1.21.12, 2.1.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 31 d ago (2026-10-08)

Exploit prediction

0.08% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
OSV	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	vault	>=1.14.0, <2.1.2	2.1.2

Affected products

HashiCorp Vault
HashiCorp Vault Enterprise

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary