CVE
HashiCorp Vault log injection in audit device prefix handling
- Exploited
- No known exploitation
- Fix
- Fixed in Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.23% · 14th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.7/10CVSS 2.7
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 25 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: Vault 2.2.2 · Vault Enterprise 2.2.2, 1.19.25, 1.21.14.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- 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
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-93333
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: cve.now feed data
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: cve.now feed data
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: cve.now feed data