Skip to main content
VulnerabilityPublished

CVE-2026-93333: HashiCorp Vault · Log Injection

Affects HashiCorp VaultSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 2.2.2 when convenient.

Data as of 12 Nov 2026, 22:51 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (HashiCorp)CVSS 3.12.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 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 12 Nov 2026.

What to do

Upgrade Vault and Vault Enterprise to 2.2.2; Vault Enterprise to 1.19.25.

Affected software

ProductAffectedFixed in
HashiCorpVaultAffected
  • >=0.7.0 <2.2.2
Fixed in
  • 2.2.2
HashiCorpVault EnterpriseAffected
  • >=0.7.0 <1.19.25
Fixed in
  • 2.2.2
GitHubVaultpkg:github/VaultOther threatsAffected
  • >=0.7.0 <2.2.2
Fixed in
  • 2.2.2
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threatsAffected
  • >=0.7.0 <1.19.25
Fixed in
  • 1.19.25

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 2.2.2, 1.21.14, or 1.19.25. Upgrading to these versions will remediate the vulnerability by properly validating audit log prefixes and enforcing server-level settings.

Description

CVE-2026-93333 is a vulnerability in HashiCorp Vault's audit devices where improper validation of audit log prefixes allows a privileged operator to inject content into audit logs. This can lead to forged or misleading 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.

References

Community reviews

Loading reviews…