CVE-2026-93333: Vault's audit devices did not validate the contents of a configured audit log prefix and did not consistently enforce…

CVE-2026-93333 · Severity: low · CVSS 2.7 · Published 2026-11-13

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.

Quick answers

Is CVE-2026-93333 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-93333 being exploited in the wild.
How severe is CVE-2026-93333?
Low severity, with a CVSS score of 2.7, published 13 November 2026.
Is there a fix for CVE-2026-93333?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-93333?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.