Vault Update Prevents New-Node Join Credential Disclosure
Tech GuruQuick Answer
Upgrade before exposing new node listeners. Move cloud auto-join configuration to retry_join and review any credentials present on previously exposed uninitialized nodes.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory integrated-storage join listeners, initialization state, cloud credentials, VAULT_TOKEN and VAULT_HEADERS in the server environment. Match edition, branch and the bulletin’s stated prerequisites before assigning exposure. Deploy the appropriate fixed Vault release through the supported upgrade procedure; validate cluster health and integrations before broad rollout. Test cluster join through the supported retry_join configuration and confirm network restrictions. Review outbound connections and preserve join, cloud and credential-use logs.
Last verified: 2026-11-13 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | HashiCorp Vault Community Edition and Vault Enterprise |
|---|---|
| Advisory | HCSEC-2026-55 |
| CVE | CVE-2026-92735 |
| Authoritative release date | 2026-11-12 — November 12, 2026 at 22:26:40 UTC, from the first-party bulletin post timestamp. |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | Vault and Vault Enterprise through 2.2.1, subject to the specific configuration and access conditions described below. |
| Fixed version | Vault Community Edition 2.2.2; Vault Enterprise 2.2.2, 1.21.14 or 1.19.25 for the supported branch |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | HashiCorp does not confirm exploitation in the wild in this bulletin.; no exploitation claim is inferred. |
What Changed
Unauthenticated requests to an uninitialized integrated-storage node can redirect environment credentials through auto-join discovery or leader contact. Initialized nodes and HA-only integrated-storage use are excluded.
What To Validate Now
- Inventory. Inventory integrated-storage join listeners, initialization state, cloud credentials, VAULT_TOKEN and VAULT_HEADERS in the server environment.
- Establish applicability. Match edition, branch and the bulletin’s stated prerequisites before assigning exposure.
- Remediate. Deploy the appropriate fixed Vault release through the supported upgrade procedure; validate cluster health and integrations before broad rollout.
- Validate. Test cluster join through the supported retry_join configuration and confirm network restrictions. Review outbound connections and preserve join, cloud and credential-use logs.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
After the fix, the join API and vault operator raft join no longer accept cloud auto-join settings. Coordinate configuration changes before adding nodes.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
