# HCSEC-2026-54 - Boundary vulnerable to server-side request forgery in Vault credential store

**URL:** <https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932>\
**Category:** Security\
**Tags:** security-boundary\
**Created:** [October 29, 2026, 9:02pm UTC](https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932 "2026-10-29T21:02:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![james.warren](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/james.warren/32/44042_2.png) [@james.warren](https://discuss.hashicorp.com/u/james.warren)\
**Post date:** [October 29, 2026, 9:02pm UTC](https://discuss.hashicorp.com/t/hcsec-2026-54-boundary-vulnerable-to-server-side-request-forgery-in-vault-credential-store/77932/1 "2026-10-29T21:02:54Z")

</div>

**Bulletin ID:** HCSEC-2026-54

**Affected Products / Versions:** Boundary and Boundary Enterprise 0.21.3 up to 1.0.1; fixed in Boundary Enterprise 1.0.2 and 0.21.6.

**Publication Date:** October 29, 2026

**Summary**

HashiCorp Boundary and Boundary Enterprise are vulnerable to a server-side request forgery in the Vault credential store integration that may allow an authenticated user with permission to manage credential stores and credential libraries within a project to cause the Boundary controller to issue outbound requests to a network destination of the requester’s choosing and to receive the response. This may expose endpoints reachable only from the controller’s host, such as a cloud instance metadata service. This vulnerability, CVE-2026-13303, is fixed in Boundary Enterprise 1.0.2 and 0.21.6.

**Background**

Boundary brokers credentials to targets by integrating with external credential sources such as HashiCorp Vault. A Vault credential store is configured with a Vault address and token, and credential libraries reference paths that the controller requests on the user’s behalf. By design, end users do not connect to these backends directly; the controller performs the outbound request from its own network position.

**Details**

The controller did not sufficiently restrict the network destination of these outbound Vault requests. A principal authorized to create or update a Vault credential store and credential library in a project could supply configuration that directed the controller to an unintended internal address and, by influencing the response, cause the controller to follow that request to a further destination and return the result to the requester. Because the controller operates from a trusted network position, this could expose information reachable only from the controller, potentially including sensitive infrastructure endpoints, a higher level of access than the requester’s project-scoped permissions are intended to grant. Exploitation requires an authenticated principal holding credential store and credential library management permissions within a project; it is not exploitable by anonymous or unauthenticated users. The fix restricts the destinations the controller will contact when servicing these requests.

Exploitation requires an authenticated principal with credential-store and credential-library management permissions within a project; it is not exploitable by anonymous or unauthenticated users.

**Remediation**

Customers should evaluate the risk associated with this issue and consider upgrading to Boundary Enterprise 1.0.2 or 0.21.6.

**Acknowledgement**

This issue was reported to HashiCorp by Owais Lone.

_We deeply appreciate any effort to coordinate disclosure of security vulnerabilities. For information about security at HashiCorp and the reporting of security vulnerabilities, please see [https://hashicorp.com/security](https://hashicorp.com/security)._