EUVD-2026-55738
GHSA-rmq8-5gxg-mjqx
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H
AV:N for network-accessible API; AC:H for required cross-namespace entity ID knowledge; PR:L for mandatory namespace authentication; S:C because impact crosses namespace isolation boundaries into other tenants.
Primary rating from Vendor (HashiCorp).
CVSS VectorVendor: HashiCorp
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Cross-namespace authorization bypass in HashiCorp Vault Enterprise's identity entity batch-delete endpoint allows an authenticated low-privileged caller in one namespace to permanently delete the storage backing of identity entities belonging to a completely separate namespace. Affected are all Vault Enterprise versions prior to the patched releases 2.0.4, 1.21.9, 1.20.14, and 1.19.20. No public exploit or CISA KEV listing has been identified at time of analysis, but the destructive, cross-tenant impact makes this a high-priority patch for any multi-namespace Vault Enterprise deployment.
Technical ContextAI
HashiCorp Vault Enterprise supports namespaces as a multi-tenancy isolation primitive, allowing distinct organizational units to operate independently within a single Vault cluster. The vulnerable component is the identity entity batch-delete API endpoint, which fails to enforce namespace boundary checks before executing deletion operations - a classic CWE-862 (Missing Authorization) defect. The affected product is identified by CPE cpe:2.3:a:hashicorp:vault_enterprise:*:*:*:*:*:*:*:*, confirming the issue is specific to the enterprise variant of Vault (namespaces are an Enterprise-only feature and are not present in open-source Vault). The root cause is that the authorization decision for the batch-delete operation does not validate whether the entity IDs submitted by the caller belong to the caller's own namespace, permitting cross-namespace targeting.
RemediationAI
Upgrade Vault Enterprise to one of the patched releases: 2.0.4, 1.19.20, 1.20.14, or 1.21.9, as confirmed by the HashiCorp advisory HCSEC-2026-27 at https://discuss.hashicorp.com/t/hcsec-2026-27-vault-enterprise-vulnerable-to-cross-namespace-entity-deletion/77634. If immediate patching is not possible, restrict access to the identity entity batch-delete endpoint via Vault ACL policies, limiting it to only highly privileged administrative principals whose namespace scope is tightly controlled - note that this reduces operational self-service capability and must be balanced against team workflows. Additionally, audit existing ACL tokens with low-privilege namespace access and review Vault audit logs for anomalous calls to the entity batch-delete path targeting entity IDs outside the caller's namespace. These compensating controls reduce exposure but do not eliminate the underlying authorization flaw.
More in Vault Enterprise
View allToken leakage in HashiCorp Vault and Vault Enterprise (0.11.2 up to 2.0.0, 1.21.5, 1.20.10, and 1.19.16) occurs when an
HashiCorp Vault's KVv2 secrets engine allows authenticated users with glob-based policy access to delete secrets outside
HashiCorp Vault unauthenticated denial-of-service vulnerability allows remote attackers to block critical administrative
Privilege escalation in HashiCorp Vault allows authenticated low-privileged users to traverse outside their authorized s
Plugin directory guard bypass in HashiCorp Vault and Vault Enterprise allows a highly privileged, authenticated attacker
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today