Audit-record forgery via unvalidated audit log prefixes
Published Nov 12, 2026 · Updated Nov 12, 2026
Log injection in HashiCorp Vault before 2.2.2 allows remote authenticated users to forge audit records via configured prefixes. Vault and Vault Enterprise audit devices prepend operator-controlled content without validating it and inconsistently enforce the server-level restriction on audit prefixing. Exploitation requires privileged audit-device configuration access; the supplied record describes misleading audit records, not code execution or secret disclosure.
Summary
What happened
Log injection in HashiCorp Vault before 2.2.2 allows remote authenticated users to forge audit records via configured prefixes. Vault and Vault Enterprise audit devices prepend operator-controlled content without validating it and inconsistently enforce the server-level restriction on audit prefixing. Exploitation requires privileged audit-device configuration access; the supplied record describes misleading audit records, not code execution or secret disclosure.
The record
- CVE
- CVE-2026-93333
- Published
- Nov 12, 2026
- Updated
- Nov 12, 2026
- Vendor
- HashiCorp
- Product
- Vault
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 12, 2026CVE publishedPublication date reported by the CVE source.
- Nov 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.7.0 <2.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us