# CVE-2026-13303: Boundary vulnerable to server-side request forgery in Vault credential store


- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-ff4v-fpcj-mjf6

## What is CVE-2026-13303?

CVE-2026-13303 is a high-severity vulnerability in HashiCorp Boundary, published on 29 Oct 2026. 

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-13303?


## How do I fix CVE-2026-13303?

No fix has been published for CVE-2026-13303 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13303 being exploited?

There is no known exploitation of CVE-2026-13303 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13303 and fix it if it is affected.

What it is: CVE-2026-13303 is a high-severity vulnerability in HashiCorp Boundary, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-13303 in the wild and no public exploit code.

Affected product: HashiCorp Boundary. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13303/ (Markdown: https://insights.sbomify.com/CVE-2026-13303/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13303
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13303
- OSV: https://osv.dev/vulnerability/CVE-2026-13303

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13303/
Summaries are generated and may contain mistakes; the official description above is the record.