CVE-2026-4525
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.
- CVSS 3.1
- 8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS
- 0.4% chance of exploitation in the next 30 days; higher than 34% of CVEs (scores of 2026-10-25)
- CWE
- CWE-201
- Published
- Modified
- Record from
- the NVD, synced
Affected
- hashicorp:vault
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-72gw-fmmr-c4r4 | Go | github.com/hashicorp/vault | >=0.11.2 <=1.21.4 | no fix published |
| GO-2026-5199 | Go | github.com/hashicorp/vault | >=0.11.2 | no fix published |
References
- https://discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344
- https://access.redhat.com/security/cve/CVE-2026-4525
- https://bugzilla.redhat.com/show_bug.cgi?id=2459107
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4525.json