Boundary vulnerable to server-side request forgery in Vault credential store
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.21.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HashiCorp Boundary and Boundary Enterprise are affected through their Vault credential store integration. An authenticated user with permission to manage credential stores and libraries could make the Boundary controller send requests to network destinations they choose and read the responses, potentially exposing services reachable only from the controller's host, such as cloud metadata endpoints.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- HashiCorp Boundary
From 0.21.3
- HashiCorp Boundary Enterprise
From 0.21.3 · fixed in 0.21.6