high7.5
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 forwarde…
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| go | github.com/hashicorp/vault | >= 0.11.2, <= 1.21.4 | none recorded |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Hashicorp | Vault | from 0.11.2 before 1.19.16 from 0.11.2 before 2.0.0 from 1.20.0 before 1.20.10 from 1.21.0 before 1.21.5 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-72gw-fmmr-c4r4
- https://nvd.nist.gov/vuln/detail/CVE-2026-4525
- 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