Vault's audit devices did not validate the contents of a configured audit log prefix and did not consistently enforce
Source GCVE Database
Not known to be exploited · CVSS 2.7 Low : upgrade to 2.2.2 when convenient.
Data as of 13 Nov 2026, 01:10 UTC
Thin evidence
One scorer or none| CNA (HashiCorp) | CVSS 3.1 | 2.7 |
|---|
- Patch
- Available – fixed in 2.2.2, 1.19.25
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 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 12 Nov 2026.
What to do
Upgrade Vault and Vault Enterprise to 2.2.2; Vault Enterprise to 1.19.25.
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
Apply the official fixes available in Vault Community Edition 2.2.2 and Vault Enterprise versions 2.2.2, 1.21.14, and 1.19.25. Upgrading to these versions will remediate the vulnerability by enforcing proper validation and restrictions on audit log prefixing.
Description
Vault's audit devices had a vulnerability where they did not validate the contents of a configured audit log prefix and inconsistently enforced the server-level restriction on audit log prefixing. This flaw could allow a privileged operator to inject misleading content into audit logs, potentially forging audit records. The issue is fixed in Vault Community Edition 2.2.2 and Vault Enterprise versions 2.2.2, 1.21.14, and 1.19.25.