HashiCorp Vault Enterprise Update Corrects Cross-Namespace ACL Resolution
Tech GuruQuick Answer
HashiCorp published HCSEC-2026-42 for Vault Enterprise through 2.1.1 with namespaces. Inventory the exact affected scope, apply Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23, validate dependent operations, and preserve change evidence.
Validate Vault Scope And Apply The Supported Fix
What to do now: Inventory Vault Enterprise through 2.1.1 with namespaces, match versions and enabled features to the authority's scope, apply supported remediation, validate representative operations, and document exceptions.
Last verified: 2026-10-08 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Vault Enterprise through 2.1.1 with namespaces |
|---|---|
| Advisory | HCSEC-2026-42 |
| CVE | CVE-2026-105820 |
| Authoritative release date | 2026-10-07 21:46:47.787 UTC |
| Authority revision date | 2026-10-07 21:46:47.787 UTC |
| Affected versions | Vault Enterprise tokens or identities able to receive specially crafted policy names while referenced policies are present in the in-memory policy cache; Community Edition does not support namespaces and is not affected. |
| Fixed version | Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Path-traversal constructs in policy names could resolve cached policies across namespace boundaries and grant unintended capabilities.
What To Validate Now
- Inventory. Locate Vault Enterprise through 2.1.1 with namespaces; record versions, enabled features, exposure paths, owners, dependencies, support channels, and maintenance groups.
- Establish applicability. Compare every deployment with the authority's affected statement: Vault Enterprise tokens or identities able to receive specially crafted policy names while referenced policies are present in the in-memory policy cache; Community Edition does not support namespaces and is not affected. Do not infer applicability from product family, CVSS, or Internet reachability alone.
- Remediate. Apply Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23 through the authority-supported channel and follow the current advisory.
- Validate. Confirm the resulting Vault build or managed state, exercise representative services and recovery paths, monitor for regressions, and retain the result.
- 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
Audit and rename policy names containing dot or dot-dot path segments before upgrading because the fixed release rejects new names and ignores those assignments on existing identities and tokens. Preserve pre-change state, installation output, logs, validation evidence, and rollback decisions.
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.
