HashiCorp Vault Enterprise up to 2.0.3/1.21.8/1.20.13/1.19.19 Identity Entity Batch-Delete Endpoint authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.83 |
Summary
A vulnerability, which was classified as critical, was found in HashiCorp Vault Enterprise up to 2.0.3/1.21.8/1.20.13/1.19.19. Affected by this issue is some unknown functionality of the component Identity Entity Batch-Delete Endpoint. Such manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-14886. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in HashiCorp Vault Enterprise up to 2.0.3/1.21.8/1.20.13/1.19.19. It has been rated as critical. Affected by this issue is some unknown functionality of the component Identity Entity Batch-Delete Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Vault Enterprise's identity entity batch-delete endpoint is vulnerable to a cross-namespace authorization bypass that may allow an authenticated caller in one namespace to permanently delete the storage backing of entities belonging to another namespace. This vulnerability (CVE-2026-14886) is fixed in Vault Enterprise 2.0.4, 1.21.9, 1.20.14 and 1.19.20.
The advisory is shared for download at discuss.hashicorp.com. This vulnerability is handled as CVE-2026-14886 since 07/06/2026. The exploitation is known to be easy. The attack may be launched remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.0.4, 1.21.9, 1.20.14 or 1.19.20 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
- 1.19.0
- 1.19.1
- 1.19.2
- 1.19.3
- 1.19.4
- 1.19.5
- 1.19.6
- 1.19.7
- 1.19.8
- 1.19.9
- 1.19.10
- 1.19.11
- 1.19.12
- 1.19.13
- 1.19.14
- 1.19.15
- 1.19.16
- 1.19.17
- 1.19.18
- 1.19.19
- 1.20.0
- 1.20.1
- 1.20.2
- 1.20.3
- 1.20.4
- 1.20.5
- 1.20.6
- 1.20.7
- 1.20.8
- 1.20.9
- 1.20.10
- 1.20.11
- 1.20.12
- 1.20.13
- 1.21.0
- 1.21.1
- 1.21.2
- 1.21.3
- 1.21.4
- 1.21.5
- 1.21.6
- 1.21.7
- 1.21.8
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Vault Enterprise 2.0.4/1.21.9/1.20.14/1.19.20
Timeline
07/06/2026 CVE reserved08/10/2026 Advisory disclosed
08/10/2026 VulDB entry created
08/10/2026 VulDB entry last update
Sources
Advisory: discuss.hashicorp.comStatus: Confirmed
CVE: CVE-2026-14886 (🔒)
GCVE (CVE): GCVE-0-2026-14886
GCVE (VulDB): GCVE-100-387872
Entry
Created: 08/10/2026 21:32Changes: 08/10/2026 21:32 (54)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.