
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-93333 is an audit log injection vulnerability in HashiCorp Vault affecting both Community Edition and Enterprise versions. Vault's audit devices failed to validate the contents of a configured audit log prefix and did not consistently enforce the server-level setting that restricts audit log prefixing, potentially allowing a privileged operator to inject content into audit logs and forge or mislead audit records. The vulnerability affects Vault and Vault Enterprise from version 0.7.0 up to (but not including) 2.2.2, and was published on November 13, 2026. It carries a CVSS v3.1 base score of 2.7 (Low) (GitHub Advisory, HashiCorp Advisory).
The root cause is classified as CWE-117 (Improper Output Neutralization for Logs): Vault's audit device subsystem constructs log messages incorporating a user-configurable prefix without sanitizing or validating special characters or injected content within that prefix. Additionally, the server-level control intended to restrict audit log prefixing was not consistently enforced across all audit device configurations. An attacker with high (operator-level) privileges can exploit this over the network by configuring a malicious audit log prefix containing crafted content — such as newline characters or structured log entries — that gets written verbatim into audit logs, enabling log forgery or tampering. No public proof-of-concept code has been identified (GitHub Advisory, HashiCorp Advisory).
Successful exploitation allows a privileged operator to inject arbitrary content into Vault's audit logs, potentially forging audit trail entries or obscuring malicious activity from security monitoring and compliance reviews. The impact is limited to integrity of audit records — there is no confidentiality or availability impact, and the vulnerability does not enable privilege escalation or lateral movement. However, in environments where Vault audit logs are relied upon for compliance, incident response, or forensic investigation, tampered logs could undermine the trustworthiness of the entire audit trail (GitHub Advisory, HashiCorp Advisory).
There is no evidence of active in-the-wild exploitation or publicly available proof-of-concept code for CVE-2026-93333. The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. Exploitation requires high privileges (operator-level access), significantly limiting the attack surface. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (GitHub Advisory, HashiCorp Advisory).
\nFake log entry: token=s.XXXXXXXX action=root_login).\n, \r, JSON fragments) that deviate from the expected prefix format.vault audit list -detailed) showing prefix values with special characters, escape sequences, or unusually long/complex strings.HashiCorp has released patches addressing this vulnerability: upgrade to Vault Community Edition 2.2.2, Vault Enterprise 2.2.2, Vault Enterprise 1.21.14, or Vault Enterprise 1.19.25. As an interim workaround prior to patching, restrict audit log prefix configuration to only the most trusted administrators and actively monitor audit log contents for anomalous entries or formatting irregularities that could indicate tampering. Reviewing and auditing existing audit device prefix configurations for suspicious values is also recommended (HashiCorp Advisory, GitHub Advisory).
HashiCorp published an official security advisory (HCSEC-2026-57) disclosing the vulnerability and providing patched versions. No notable independent researcher commentary, social media discussion, or significant media coverage has been identified for this low-severity vulnerability at this time (HashiCorp Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."