CVE-2025-6000VaultFault, first public HashiCorp Vault RCE
What broke
HashiCorp Vault could be pushed into remote code execution through plugin-catalog and audit-log abuse. Cyata reported the set in May 2025, IDs were assigned 12 June, and the public write-up (HCSEC-2025-22, "VaultFault") landed on 6 August 2025 at Black Hat USA. This one is the first public Vault RCE. The bug had been in the product for about nine years. CVSS 9.1. Fixed in Vault CE 1.20.2 and Enterprise 1.20.2 / 1.19.8 / 1.18.13 / 1.16.24.
Why it matters
Vault is the identity plane for secrets, cloud IAM, and often SSH and PKI. RCE on Vault is every secret, every dynamic credential, and the root token story you hoped you would never write. Nine years in-tree is also the process lesson: identity infrastructure ages, and "it has always been that way" is not a control.
What to do
- Upgrade to 1.20.2 (or the Enterprise train that includes HCSEC-2025-22) before you do anything else on this list.
- Rotate secrets Vault issued or stored. If the plugin catalog was writable, assume RCE was possible.
- Restrict who can manage plugins. The catalog is not an AppSec curiosity. It is root on the secrets plane.
Sources
- NVD: CVE-2025-6000
- HashiCorp HCSEC-2025-22 / Cyata VaultFault, Black Hat USA 2025