Read the docs

Log injection in HashiCorp Vault audit log prefix

Priority LOW 13CWE-117Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

HashiCorp Vault and Vault Enterprise from 0.7.0 before 2.2.2 do not validate the contents of a configured audit log prefix, and they do not consistently enforce the server-level setting that restricts audit log prefixing. A privileged operator can inject content into audit logs, which can produce forged or misleading audit records (CWE-117).

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Vault's audit devices did not validate the contents of a configured audit log prefix and did not consistently enforce the server-level setting that restricts audit log prefixing. This may allow a privileged operator to inject content into audit logs, potentially leading to forged or misleading audit records. This vulnerability (CVE-2026-93333) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00231 14th percentileScored 2026-11-16
Fix Fixed Vault (HashiCorp): 2.2.2Vault Enterprise (HashiCorp): 2.2.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
HashiCorpVault0.7.0 to before 2.2.22.2.2Patch availableCNA
HashiCorpVault Enterprise0.7.0 to before 2.2.22.2.2Patch availableCNA
  • Vault VendorHashiCorp Affected 0.7.0 to before 2.2.2 Fixed in 2.2.2 Patch available CNA
  • Vault Enterprise VendorHashiCorp Affected 0.7.0 to before 2.2.2 Fixed in 2.2.2 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:hashicorp:vault:*:*:*:*:*:*:*:*——HashiCorp
  • cpe:2.3:a:hashicorp:vault:*:*:*:*:*:*:*:* Versions — — ·HashiCorp

Remediation

Upgrade Vault Community Edition to 2.2.2. Upgrade Vault Enterprise to 2.2.2, 1.21.14, or 1.19.25.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA Vault (HashiCorp) Fixed in 2.2.2
  • Fix · CNA Vault Enterprise (HashiCorp) Fixed in 2.2.2

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    HashiCorp Vault, Vault Enterprise 2.2.2

    3 records Highest priority Priority LOW 3 LOW

    Other records, highest priority first

    • TI-2026-91055 Trailing slash bypasses ACL deny rules in HashiCorp VaultPriority LOW 29
    • TI-2026-91053 Vault integrated storage join may leak server environment credentialsPriority LOW 26

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-93333
  2. 2026-11-13 Alias added: GHSA-w4qh-g6vc-38wx
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2024-01904 Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates CVSS 3.1CRITICAL 9.8
  • TI-2021-18437 HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4… CVSS 3.1HIGH 8.8
  • TI-2026-06570 Nomad vulnerable to path traversal in dynamic host volume which may lead to code execution CVSS 3.1HIGH 8.8
  • TI-2020-17753 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root… CVSS 3.1CRITICAL 9.8
  • TI-2026-13641 consul-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
  • TI-2026-13778 terraform-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode CVSS 3.1CRITICAL 10.0
See all 252 →

Sources