Privileged host code execution via audit-file planting
Published Aug 1, 2025 · Updated Aug 1, 2025
Code injection in HashiCorp Vault before 1.20.1 and affected Vault Enterprise releases allows remote authenticated users to execute host code. The file audit device writes operator-controlled bytes into a configured plugin directory, while sys/audit-hash reveals the digest needed to register and run that file as an external plugin. Exploitation requires root-namespace write access to sys/audit and a configured plugin directory, and grants code execution on the underlying host.
Summary
What happened
Code injection in HashiCorp Vault before 1.20.1 and affected Vault Enterprise releases allows remote authenticated users to execute host code. The file audit device writes operator-controlled bytes into a configured plugin directory, while sys/audit-hash reveals the digest needed to register and run that file as an external plugin. Exploitation requires root-namespace write access to sys/audit and a configured plugin directory, and grants code execution on the underlying host.
The record
- CVE
- CVE-2025-6000
- Published
- Aug 1, 2025
- Updated
- Aug 1, 2025
- Vendor
- HashiCorp
- Product
- Vault
- Classifications
- CWE-94, CAPEC-549, T1210
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 1, 2025CVE publishedPublication date reported by the CVE source.
- Aug 1, 2025Record 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.8.0 <1.20.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo