CVE-2026-4525: HashiCorp Vault · Insertion of Sensitive Information Into Sent Data
Affects HashiCorp VaultSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 2.0.0 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.0, 1.19.16
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Vault and Vault Enterprise to 2.0.0; Vault Enterprise to 1.19.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HashiCorpVault | Affected
| Fixed in
|
| HashiCorpVault Enterprise | Affected
| Fixed in
|
GitHubVaultpkg:github/VaultOther threats | Affected
| Fixed in
|
GitHubVault Enterprisepkg:github/Vault EnterpriseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions are available: 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Users should upgrade to one of these versions to remediate the vulnerability. Patch status is confirmed by the vendor advisory. No additional mitigations are specified.
Description
If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
References
- discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-4525 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2459107 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4525.json (opens in a new tab)