Security Bulletin
Summary
HashiCorp Vault and Vault Enterprise are vulnerable to an issue in the integrated storage join process that may allow an unauthenticated attacker with network access to a new, uninitialized node to cause that node to send credentials from its server environment to an attacker-controlled server. This vulnerability (CVE-2026-92735) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25.
Vulnerability Details
CVEID: CVE-2026-92735
DESCRIPTION: Vault's join API accepted cloud auto-join discovery settings supplied in an unauthenticated request. For discovery providers that allow the provider API endpoint to be specified and that read credentials from the server environment, an attacker could direct the node to send those credentials to a server under the attacker's control. In addition, when contacting a leader node specified in a join request, Vault included any Vault token, and in Vault 1.18.0 and later any custom headers, configured through the VAULT_TOKEN and VAULT_HEADERS environment variables of the Vault server process. The issue requires network access to the API listener of a node that uses integrated storage and has not yet been initialized, but does not require authentication. Exposure depends on such credentials being present in the Vault server's environment. Initialized nodes, and nodes that use integrated storage only for high availability, are not affected.
CWE: CWE-918: Server-Side Request Forgery (SSRF)
CVSS Source: HashiCorp Inc.
CVSS Base score: 5.9
CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
Affected Products and Versions
| Affected Product(s) | Version(s) |
| Vault Community Edition | affected from 1.2.0 up to 2.2.2 |
| Vault Enterprise | affected from 1.2.0 up to 2.2.2, unaffected from 1.19.25, 1.21.14 |
Remediation/Fixes
Customers should evaluate the risk associated with this issue and consider upgrading to Vault Community Edition 2.2.2 or Vault Enterprise 2.2.2, 1.21.14, or 1.19.25. After upgrading, the join API and the vault operator raft join command no longer accept cloud auto-join settings, so operators who rely on them should configure cloud auto-join using the retry_join stanza in the integrated storage configuration. Restricting network access to the API listener of new Vault nodes until they have joined a cluster reduces exposure to this issue.
Get Notified about Future Security Bulletins
References
Acknowledgement
This issue was reported to HashiCorp by Tal Vaknin, Independent Security Researcher.
Change History
12 Nov 2026: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
12 November 2026
Initial Publish date:
12 November 2026
UID
ibm17296634