HashiCorp Vault/Vault Enterprise up to 1.21.0 Header Authorization insertion of sensitive information into sent data

Summaryinfo

A vulnerability, which was classified as problematic, was found in HashiCorp Vault and Vault Enterprise. Affected by this issue is some unknown functionality of the component Header Handler. The manipulation of the argument Authorization results in insertion of sensitive information into sent data. This vulnerability is identified as CVE-2026-4525. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in HashiCorp Vault and Vault Enterprise. Affected is some unknown functionality of the component Header Handler. The manipulation of the argument Authorization with an unknown input leads to a insertion of sensitive information into sent data vulnerability. CWE is classifying the issue as CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at discuss.hashicorp.com. This vulnerability is traded as CVE-2026-4525 since 03/20/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 2.0.0 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• HashiCorp

Name

• Vault
• Vault Enterprise

Version

• 1.2.5
• 1.3.4
• 1.3.6
• 1.3.7
• 1.3.8
• 1.4.0
• 1.4.1
• 1.4.2
• 1.4.3
• 1.4.4
• 1.5.0
• 1.5.1
• 1.5.6
• 1.5.7
• 1.5.8
• 1.5.9
• 1.6.0
• 1.6.1
• 1.6.2
• 1.6.3
• 1.6.4
• 1.6.5
• 1.6.6
• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.8.0
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.9.0
• 1.9.1
• 1.9.10
• 1.10.0
• 1.10.1
• 1.10.2
• 1.10.3
• 1.10.6
• 1.10.7
• 1.10.11
• 1.11.3
• 1.11.4
• 1.11.7
• 1.11.8
• 1.11.9
• 1.12.0
• 1.12.3
• 1.12.4
• 1.12.5
• 1.12.11
• 1.13.0
• 1.13.1
• 1.13.5
• 1.13.7
• 1.13.8
• 1.13.9
• 1.13.10
• 1.14.0
• 1.14.1
• 1.14.3
• 1.14.4
• 1.14.5
• 1.14.6
• 1.14.10
• 1.15
• 1.15.0
• 1.15.1
• 1.15.2
• 1.15.4
• 1.15.15
• 1.16.0
• 1.16.9
• 1.16.10
• 1.17.5
• 1.17.6
• 1.18.0
• 1.18.1
• 1.20.0
• 1.20.1
• 1.20.2
• 1.21.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion