Review reviewHigh

CVE-2026-4525

HashiCorp Vault, Vault Enterprise, Red Hat OpenShift Container Platform 4

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
8.8
EPSS
0.41%
33.3% percentile
CISA KEV
Not listed
Published
2026.04.17
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.41%
Technical severityCVSS 8.8

Vulnerability overview

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 product and versions

Product
HashiCorp Vault, Vault Enterprise, Red Hat OpenShift Container Platform 4
Affected versions
>= 0.11.2 < 2.0.0, >= 0.11.2 < 1.19.16, >= 1.20.0 < 1.20.10, >= 1.21.0 < 1.21.5
Fixed versions
1.19.16, 2.0.0, 1.20.10, 1.21.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that HashiCorp Vault, Vault Enterprise, Red Hat OpenShift Container Platform 4 and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-201