CVE-2026-93333

Description

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.

Severity
LOW
CVSS v3
2.7
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N · source cna
Exploit chance (EPSS)
0.231%
chance of exploitation in the next 30 days
higher than 14.1% of scored CVEs · 2026-11-18
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impactpartial
Scored2026-11-13

Timeline

  1. 2026-11-12Published by the CNA22:32 UTC
  2. 2026-11-13CISA SSVC decision recorded1 day after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
hashicorp vaultfrom 0.7.0 before 2.2.2fixed in 2.2.22.2.2
hashicorp vault_enterprisefrom 0.7.0 before 2.2.2fixed in 2.2.22.2.2

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources