CVE-2026-105816: HashiCorp Vault · Path Traversal
Affects HashiCorp VaultSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 2.1.2 soon.
Data as of 21 Nov 2026, 17:34 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% 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:H/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorpVault | Affected
| Fixed in
|
| HashiCorpVault Enterprise | Affected
| Fixed in
|
GitHubVaultpkg:github/VaultOther threats | Affected
| Fixed in
|
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability 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. Users should upgrade to these versions or later to remediate the issue. No other mitigation or workaround is specified.
Description
CVE-2026-105816 is a path traversal vulnerability in HashiCorp Vault and Vault Enterprise that allows a privileged operator to execute arbitrary code on the Vault host when restoring an Integrated Storage (Raft) snapshot with an external plugin directory configured. The issue arises because Vault did not consistently verify that plugin catalog entries reference binaries only within the configured plugin directory. This vulnerability has a high severity score of 8.0 and 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.