CVE-2026-7776

Boundary Community Edition and Boundary Enterprise ("Boundary") workers are vulnerable to a denial-of-service condition during node enrollment TLS handshakes. An attacker with network access to the worker authentication listener may open a connection and delay or withhold the client certificate during the TLS handshake, causing worker connection handling to block. This may prevent legitimate worker connections from being accepted or routed. This vulnerability, CVE-2026-7776, is fixed in Boundary 0.21.3, 0.20.3, 0.19.5.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2026-7776 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.19.5, 0.20.3, 0.21.3); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-7776? CVE-2026-7776 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/hashicorp/boundary (go), affecting versions < 0.19.5. It is fixed in 0.19.5, 0.20.3, 0.21.3. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2026-7776? CVE-2026-7776 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/hashicorp/boundary are affected by CVE-2026-7776? github.com/hashicorp/boundary (go) versions < 0.19.5 is affected.
4. Is there a fix for CVE-2026-7776? Yes. CVE-2026-7776 is fixed in 0.19.5, 0.20.3, 0.21.3. Upgrade to this version or later.
5. Is CVE-2026-7776 exploitable, and should I be worried? Whether CVE-2026-7776 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-7776 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-7776?
   • Upgrade github.com/hashicorp/boundary to 0.19.5 or later
   • Upgrade github.com/hashicorp/boundary to 0.20.3 or later
   • Upgrade github.com/hashicorp/boundary to 0.21.3 or later