Is CVE-2026-4525 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-4525 being exploited in the wild.

How severe is CVE-2026-4525?

High severity, with a CVSS score of 7.5, published 17 April 2026.

Which products and versions are affected?

github.com/hashicorp/vault (Go) >= 0.11.2, <= 1.21.4, SEMVER:introduced=0.11.2, SEMVER:introduced=0.11.2,last_affected=1.21.4; HashiCorp Vault Community Edition 0.11.2 - 1.21.4, 0.11.2 to 1.21.4; HashiCorp Vault Enterprise 0.11.2 - 1.19.15, 1.20.0 - 1.20.9, 1.21.0 - 1.21.4, 0.11.2 to 1.19.15, 1.20.9, 1.21.4, 0.11.2 to 1.21.4, 1.20.9, 1.19.15; Red Hat OpenShift Data Foundation 4 4.

Is there a fix for CVE-2026-4525?

A patch was published on 2026-04-17: Fixed versions released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-4525 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-4525?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition, HashiCorp Vault Enterprise or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-4525: HashiCorp Vault token disclosure in auth plugin header forwarding

Q: Is there a fix for CVE-2026-4525?

A patch was published on 2026-04-17: Fixed versions released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-4525 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-4525?

Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition, HashiCorp Vault Enterprise or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-4525 · Severity: high · CVSS 7.5 · Published 2026-04-17

HashiCorp Vault, a tool for managing sensitive secrets and credentials, contains a flaw that could accidentally leak authentication tokens to third-party plugins. If a plugin is configured to receive certain network headers, Vault may fail to remove its own security token before forwarding the request, potentially allowing a malicious or compromised plugin to impersonate users. This could lead to unauthorized access to sensitive corporate data or administrative functions.

Technologies: github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition, HashiCorp Vault Enterprise, Red Hat OpenShift Data Foundation 4. Vendors: Go, HashiCorp, Red Hat.

Quick answers

Is CVE-2026-4525 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-4525 being exploited in the wild.
How severe is CVE-2026-4525?: High severity, with a CVSS score of 7.5, published 17 April 2026.
Which products and versions are affected?: github.com/hashicorp/vault (Go) >= 0.11.2, <= 1.21.4, SEMVER:introduced=0.11.2, SEMVER:introduced=0.11.2,last_affected=1.21.4; HashiCorp Vault Community Edition 0.11.2 - 1.21.4, 0.11.2 to 1.21.4; HashiCorp Vault Enterprise 0.11.2 - 1.19.15, 1.20.0 - 1.20.9, 1.21.0 - 1.21.4, 0.11.2 to 1.19.15, 1.20.9, 1.21.4, 0.11.2 to 1.21.4, 1.20.9, 1.19.15; Red Hat OpenShift Data Foundation 4 4.
Is there a fix for CVE-2026-4525?: A patch was published on 2026-04-17: Fixed versions released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-4525 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-4525?: Check whether you run github.com/hashicorp/vault (Go), HashiCorp Vault Community Edition, HashiCorp Vault Enterprise or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in HashiCorp Vault (CVE-2026-4525) stems from incorrect header sanitization in the request processing logic. When a Vault auth mount is configured with 'passthrough_request_headers' including the 'Authorization' header, and that same header is used for Vault authentication, the service fails to strip the Vault token before forwarding the request to the auth plugin backend. An attacker with low privileges could potentially capture these tokens if they control or can monitor the plugin backend. The vulnerability is mitigated by a fix that explicitly strips the Vault token from forwarded headers regardless of configuration. Patches are available in versions 2.0.0, 1.21.5, 1.20.10, and 1.19.16.

Affected products

HashiCorp Vault Community Edition 0.11.2 to 1.21.4
HashiCorp Vault Enterprise 0.11.2 to 1.21.4, 1.20.9, 1.19.15

Identifiers

CVE-2026-4525
GHSA-72gw-fmmr-c4r4
GO-2026-5199

Timeline

2026-04-16: advisory: HashiCorp internal publication date
2026-04-17: disclosed: Public disclosure and CVE assignment
2026-04-17: patched: Fixed versions released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.