{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-13303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-13303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-13303 is a high-severity vulnerability in HashiCorp Boundary, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-13303 and fix it if it is affected.\n\nWhat it is: CVE-2026-13303 is a high-severity vulnerability in HashiCorp Boundary, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-13303 in the wild and no public exploit code.\n\nAffected product: HashiCorp Boundary. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-13303/ (Markdown: https://insights.sbomify.com/CVE-2026-13303/index.md)","id":"CVE-2026-13303","markdown":"https://insights.sbomify.com/CVE-2026-13303/index.md","name":"CVE-2026-13303","record":{"aliases":["GHSA-ff4v-fpcj-mjf6"],"analysis":null,"analysis_generated_by":null,"assigner":"HashiCorp","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Boundary vulnerable to server-side request forgery in Vault credential store","id":"CVE-2026-13303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in MaxiCharger AC Elite Home","id":"CVE-2026-13305"},"packages":[],"prev":{"headline":"Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-13297"},"products":["Boundary","Boundary Enterprise"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["HashiCorp"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-13303/"}