Skip to main content
VulnerabilityPublished

CVE-2026-105818: HashiCorp Vault · Insufficient Verification of Data Authenticity

Affects HashiCorp VaultSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.1.2 when convenient.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.2, 1.21.12
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade Vault and Vault Enterprise to 2.1.2; Vault Enterprise to 1.21.12.

Affected software

ProductAffectedFixed in
HashiCorpVaultAffected
  • >=1.14.0 <2.1.2
Fixed in
  • 2.1.2
HashiCorpVault EnterpriseAffected
  • >=1.14.0 <1.21.12
Fixed in
  • 2.1.2
GitHubVaultpkg:github/VaultOther threatsAffected
  • >=1.14.0 <2.1.2
Fixed in
  • 2.1.2
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threatsAffected
  • >=1.14.0 <1.21.12
Fixed in
  • 1.21.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official fixes provided by HashiCorp by upgrading to Vault Community Edition 2.1.2 or Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23. These versions address the insufficient verification of certificate identities in the ACME server. No other mitigation steps are indicated by the vendor advisory.

Description

HashiCorp Vault's PKI secrets engine ACME server had a vulnerability where it did not restrict certificate identities that were not validated by ACME challenges under the default directory policy. This could allow an ACME client to obtain a certificate with unverified identity claims, potentially enabling impersonation against systems trusting certificates from the affected Vault PKI mount. The issue is fixed in Vault Community Edition 2.1.2 and Vault Enterprise versions 2.1.2, 1.21.12, 1.20.17, and 1.19.23.

References

Community reviews

Loading reviews…