HashiCorp Boundary Updates Fix Vault Credential-Store SSRF
Tech GuruQuick Answer
HashiCorp HCSEC-2026-54 affects Boundary 0.21.3 through 1.0.1 when a principal can manage Vault credential stores and libraries. Inventory controllers and delegated roles, update to 1.0.2 or 0.21.6, validate credential brokering and egress controls, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory Boundary controllers, exact release branches, Vault credential stores and libraries, project principals with management permissions, reachable internal and metadata endpoints, owners, and maintenance windows. Confirm both an affected release and the required credential-store and library permissions; anonymous users and principals without that delegated management path are not in the stated scope. Upgrade to Boundary Enterprise 1.0.2 or 0.21.6 through the supported channel and review least-privilege and outbound network controls for controllers. Confirm controller versions, test Vault credential brokering and project authorization, validate egress restrictions, review unusual controller requests where warranted, and retain configuration and change evidence.
Last verified: 2026-10-30 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | HashiCorp Boundary and Boundary Enterprise Vault credential-store integration |
|---|---|
| Advisory | HCSEC-2026-54 |
| CVE | CVE-2026-13303 |
| Authoritative release date | 2026-10-29 21:02:54 UTC |
| Authority revision date | 2026-10-29 21:02:54 UTC |
| Affected versions | Boundary and Boundary Enterprise 0.21.3 through 1.0.1 when an authenticated principal can manage Vault credential stores and libraries within a project. |
| Fixed version | Boundary Enterprise 1.0.2 or 0.21.6 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | HashiCorp does not state that this vulnerability is being maliciously exploited.; no exploitation claim is inferred. |
What Changed
HashiCorp fixed server-side request forgery that could make a Boundary controller request attacker-chosen internal destinations and return responses to an authorized project principal.
What To Validate Now
- Inventory. Inventory Boundary controllers, exact release branches, Vault credential stores and libraries, project principals with management permissions, reachable internal and metadata endpoints, owners, and maintenance windows.
- Establish applicability. Confirm both an affected release and the required credential-store and library permissions; anonymous users and principals without that delegated management path are not in the stated scope.
- Remediate. Upgrade to Boundary Enterprise 1.0.2 or 0.21.6 through the supported channel and review least-privilege and outbound network controls for controllers.
- Validate. Confirm controller versions, test Vault credential brokering and project authorization, validate egress restrictions, review unusual controller requests where warranted, and retain configuration and change evidence.
- 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
Boundary controllers can reach trusted infrastructure and credential systems. Preserve request and audit evidence before changes when abuse is suspected and do not break required Vault connectivity with untested egress rules.
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.
