CyberSecBulletin
CVE-2026-4525NVD status: Modified

Vault: Insertion of Sensitive Information Into Sent Data

CVE-2026-4525 is a high-severity insertion of sensitive information into sent data vulnerability in Vault from HashiCorp, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.0.0 as the first without the flaw, so updating Vault to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Vault to 2.0.0 or a later version.
  2. Update Vault Enterprise to 2.0.0 or a later version.
  3. Read the advisory on discuss.hashicorp.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
HashiCorpVault0.11.2 up to, but not including, 2.0.02.0.0
HashiCorpVault Enterprise0.11.2 up to, but not including, 2.0.02.0.0
Red HatRed Hat OpenShift Container Platform 4Not specified in the recordNot stated
Red HatRed Hat Openshift Data Foundation 4Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (hashicorp.com)
CVSS 3.18.8HighNVD
CVSS 3.17.5HighCNA

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How developers prevent this class of flaw

  • Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
  • Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
  • Setup default error messages so that unexpected errors do not disclose sensitive information.

More Insertion of Sensitive Information Into Sent Data vulnerabilities (CWE-201)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Vault

All Vault vulnerabilities

Recent Insertion of Sensitive Information Into Sent Data vulnerabilities

Spotted an error? Tell us.