GHSA-H58C-XCCX-75M3

Coder: Stored HTML injection via unescaped ApplicationName and LogoURL appearance settings

The ApplicationName and LogoURL appearance settings were rendered into HTML output without sufficient escaping which let a highly privileged Owner-role user inject HTML into the Coder dashboard and SMTP notification emails.

Note: Exploitation requires the Owner role which already holds full administrative control of the deployment so practical impact is limited.

Workarounds

Restrict the Owner role to trusted administrators.

References

• Fix: #25804

Credits

We'd like to thank Anthropic's Security Team (ANT-2026-22453) for independently disclosing this issue!

An Owner-role user could store HTML markup in the ApplicationName or LogoURL appearance settings that later rendered in the dashboard and in SMTP notification emails which results in stored HTML injection against other users of the deployment. Exploitation requires the highly privileged Owner role.

GHSA-H58C-XCCX-75M3 has a CVSS score of 3.4 (Low). The vector is network-reachable, high privileges required, and user interaction required. 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 (2.34.2, 2.33.8, 2.32.7, 2.29.17); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The fix escapes the ApplicationName and LogoURL appearance values in HTML output before rendering.

The fix was backported to all supported release lines:

1. What is GHSA-H58C-XCCX-75M3? GHSA-H58C-XCCX-75M3 is a low-severity security vulnerability in github.com/coder/coder/v2 (go), affecting versions >= 2.34.0, < 2.34.2. It is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17.
2. How severe is GHSA-H58C-XCCX-75M3? GHSA-H58C-XCCX-75M3 has a CVSS score of 3.4 (Low). 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/coder/coder/v2 are affected by GHSA-H58C-XCCX-75M3? github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.
4. Is there a fix for GHSA-H58C-XCCX-75M3? Yes. GHSA-H58C-XCCX-75M3 is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.
5. Is GHSA-H58C-XCCX-75M3 exploitable, and should I be worried? Whether GHSA-H58C-XCCX-75M3 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 GHSA-H58C-XCCX-75M3 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 GHSA-H58C-XCCX-75M3?
   • Upgrade github.com/coder/coder/v2 to 2.34.2 or later
   • Upgrade github.com/coder/coder/v2 to 2.33.8 or later
   • Upgrade github.com/coder/coder/v2 to 2.32.7 or later
   • Upgrade github.com/coder/coder/v2 to 2.29.17 or later

Other vulnerabilities in github.com/coder/coder/v2