CVE-2026-4525: CWE-201: Insertion of Sensitive Information Into Sent Data in HashiCorp Vault
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.
AI Analysis
Technical Summary
This vulnerability involves the insertion of sensitive information (Vault token) into sent data when Vault is configured to pass through the "Authorization" header for authentication. Specifically, Vault forwards the Vault token to the auth plugin backend, potentially exposing sensitive authentication tokens. The vulnerability is tracked as CWE-201 (Insertion of Sensitive Information Into Sent Data). It affects Vault versions prior to the fixed releases 2.0.0, 1.21.5, 1.20.10, and 1.19.16. The CVSS v3.1 score is 7.5, indicating a high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requiring low privileges but high attack complexity.
Potential Impact
An attacker able to interact with a Vault auth mount configured as described could receive forwarded Vault tokens, potentially leading to unauthorized access or token leakage. The vulnerability impacts confidentiality, integrity, and availability of Vault data. There are no known exploits in the wild at this time.
Mitigation Recommendations
Fixed versions are available: 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Users should upgrade to one of these versions to remediate the vulnerability. Patch status is confirmed by the vendor advisory. No additional mitigation is indicated beyond applying the official fix.
CVE-2026-4525: CWE-201: Insertion of Sensitive Information Into Sent Data in HashiCorp Vault
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability involves the insertion of sensitive information (Vault token) into sent data when Vault is configured to pass through the "Authorization" header for authentication. Specifically, Vault forwards the Vault token to the auth plugin backend, potentially exposing sensitive authentication tokens. The vulnerability is tracked as CWE-201 (Insertion of Sensitive Information Into Sent Data). It affects Vault versions prior to the fixed releases 2.0.0, 1.21.5, 1.20.10, and 1.19.16. The CVSS v3.1 score is 7.5, indicating a high severity with network attack vector, high impact on confidentiality, integrity, and availability, and requiring low privileges but high attack complexity.
Potential Impact
An attacker able to interact with a Vault auth mount configured as described could receive forwarded Vault tokens, potentially leading to unauthorized access or token leakage. The vulnerability impacts confidentiality, integrity, and availability of Vault data. There are no known exploits in the wild at this time.
Mitigation Recommendations
Fixed versions are available: 2.0.0, 1.21.5, 1.20.10, and 1.19.16. Users should upgrade to one of these versions to remediate the vulnerability. Patch status is confirmed by the vendor advisory. No additional mitigation is indicated beyond applying the official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- HashiCorp
- Date Reserved
- 2026-03-20T17:47:40.835Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e2142082d89c981fcd7c24
Added to database: 4/17/2026, 11:06:08 AM
Last enriched: 4/17/2026, 11:06:33 AM
Last updated: 4/17/2026, 5:34:06 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.