CVE-2026-92735: Vault integrated storage join may disclose server environment credentials
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: HashiCorp Vault 2.2.2; HashiCorp Vault Enterprise 1.19.25, 1.21.14, 2.2.2.
Low priority for now. Upgrade to HashiCorp Vault 2.2.2; HashiCorp Vault Enterprise 1.19.25, 1.21.14, 2.2.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-918
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HashiCorp
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Vault
- 1.2.0 and later · before 2.2.2affected · semver
HashiCorp Vault Enterprise
- 1.2.0 and later · before 2.2.2affected · semverfixed in 1.19.25, 1.21.14
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-35192The official vault docker images before 0.11.6 contain a blank password for a root user.40Plan
- CVE-2024-2048Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates39Monitor
- CVE-2020-12757HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-105818Oct 7, 2026 · Vault PKI ACME Issues Certificate With Unvalidated SANs23Monitor
- ← EarlierCVE-2026-89322Oct 7, 2026 · Vault ACL Policy Evaluation May Allow Bypass of Deny Restrictions28Monitor
- Later →CVE-2026-93333Nov 13, 2026 · Vault audit device prefix vulnerable to log injection10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Vault | 2.2.2 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.19.25 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 1.21.14 | Vendor (CNA) |
| HashiCorp Vault Enterprise | 2.2.2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Fix recordedsame day
- Published
- TodayNov 16, 2026+3 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-5052210 days apartVault Vulnerable to Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS34Monitor
Not on record for this CVE: patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.