GPU VulnDB

Database/Control plane, storage & DevOps

HashiCorp Vault: new uninitialized node can be tricked into sending its server credentials to an attacker

CVSS 5.9CVE-2026-92735Control plane, storage & DevOpscurated

Impact

While a new, uninitialized Vault node is joining integrated storage, an attacker who can reach it over the network can make it send credentials from its server environment to a server the attacker controls. Depending on how the node is deployed, those could be cloud or platform credentials that reach beyond Vault. Already-initialized nodes are not described as affected. The exposure is limited to the window when nodes are being added or rebuilt.

Who can reach it

Unauthenticated attacker with network access to a new, uninitialized Vault node. Attack complexity is high.

What to do

Upgrade to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14 or 1.19.25. Do a rolling upgrade of each server with a daemon restart, standbys first. Until then, keep new nodes off untrusted networks until they have joined. If an uninitialized node may have been exposed, rotate the credentials in its environment.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.