Live › vulnerability › CVE-2026-13303
Boundary's Vault credential store integration can be made to send outbound requests to a destination chosen by the requester and return the response. An attacker with credential-management rights can use the controller to read services reachable only from the controller's host, such as a cloud metadata service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 21:26 UTC. All times on this page are UTC.
Only deployments of Boundary or Boundary Enterprise that use the Vault credential store integration are exposed. The attacker needs an account with permission to manage credential stores and credential libraries within a project. Teams not using the Vault integration or without such accounts are less exposed, but the sources do not say whether the flaw needs the Vault integration enabled.
No product ranges from the sources yet.
boundary version1.0.2 and 0.21.6Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-13303")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.