HashiCorp has issued a high-severity advisory (HCSEC-2025-14) detailing CVE-2025-6000, a vulnerability that allows a privileged Vault operator to achieve remote code execution on the host running Vault.
The weakness affects Vault Community Edition and Vault Enterprise versions 0.8.0 through 1.20.0, with fixes released in Community 1.20.1 and Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.
Published on 1 August 2025, the bulletin warns that an attacker who already has write access to the sys/audit endpoint in the root namespace can chain the file-writing capabilities of Vault’s file audit device with the plugin registration workflow to run arbitrary binaries on the underlying server.
Audit devices in Vault capture a complete log of every request and response. They support options for per-line prefixes and flexible on-disk storage locations.
External plugins, meanwhile, execute as standalone processes spawned and managed by Vault over RPC. Although both components are normally benign, their interaction in specific configurations exposes an unexpected path to full system compromise.
HashiCorp Vulnerability
The exploit hinges on two misused features:
- File audit device write abuse — An operator with write rights to
sys/auditcan configure a file audit device that writes crafted log lines to an arbitrary path on disk. By directing this output into Vault’s plugin directory, the operator effectively places custom executable code where Vault expects legitimate plugins. - Digest verification bypass — When Vault mounts a plugin, it verifies the SHA-256 digest provided during registration. The advisory notes that operators can obtain the exact hash for the rogue “audit log” file by replaying the data through the
sys/audit-hashendpoint, which uses a per-device HMAC key. With the correct digest in hand, the attacker satisfies Vault’s integrity check and successfully activates the malicious payload.
Once the plugin is mounted, Vault spawns it with the privileges of the Vault process, granting the attacker code execution on the host OS. The attack requires no vulnerability in the plugin interface itself—only legitimate configuration calls that administrators routinely perform.
HashiCorp confirms the issue cannot be exploited on HCP Vault Dedicated, where administrative namespaces fence high-risk system endpoints away from tenant operators.
Environments running self-managed Vault clusters, however, face elevated danger if operators are overly-privileged or RBAC policies are loosely defined.
Mitigations
HashiCorp’s fix makes two key changes:
- Prefix restriction — The
prefixoption for new audit devices is now disabled by default. Operators must explicitly setAllowAuditLogPrefixing = truein the server configuration to re-enable it, reducing the risk of path manipulation. - Destination hardening — Audit logs can no longer point to the plugin directory, blocking the simplest route to drop executables in a trusted location.
Administrators should upgrade immediately to a patched release:
- Vault Community Edition 1.20.1
- Vault Enterprise 1.20.1, 1.19.7, 1.18.12, or 1.16.23
Before upgrading, review the standard Upgrading Vault guide, paying attention to any breaking changes between minor versions.
By combining these interim controls with the vendor’s patches, operators can sharply reduce the window in which CVE-2025-6000 is exploitable.
Organizations that cannot patch right away should:
- Audit and tighten RBAC so that write access to
sys/auditexists only for automation accounts and a minimal set of administrators. - Verify that no audit devices write to directories also used for plugins or executables.
- Disable unused external plugin functionality or isolate plugins in dedicated directories with restrictive permissions.
Finally, monitor logs for suspicious audit device configurations or unexpected plugin registrations—both actions should be rare in stable environments.
Find this Story Interesting! Follow us on LinkedIn and X to Get More Instant Updates.
.webp?w=356&resize=356,220&ssl=1)




