Coder: Stored HTML injection via unescaped ApplicationName and LogoURL appearance settingsGHSA-h58c-xccx-75m3
LOWFix: coder/coder#25804GHSA-h58c-xccx-75m3 is a low-severity (CVSS 3.4) Cross-site Scripting (XSS) vulnerability in github.com/coder/coder/v2. A fix is available for github.com/coder/coder/v2 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-h58c-xccx-75m3.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/coder/coder/v2🐹github.com/coder/coder/v2🐹github.com/coder/coder/v2🐹github.com/coder/coder/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
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
Ownerrole which already holds full administrative control of the deployment so practical impact is limited.
Impact
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.
Patches
The fix escapes the ApplicationName and LogoURL appearance values in HTML output before rendering.
The fix was backported to all supported release lines:
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!
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/coder/coder/v2 | ≥ 2.34.0&&< 2.34.2 | 2.34.2go get github.com/coder/coder/v2@v2.34.2 |
| 🐹Go | github.com/coder/coder/v2 | ≥ 2.33.0&&< 2.33.8 | 2.33.8go get github.com/coder/coder/v2@v2.33.8 |
| 🐹Go | github.com/coder/coder/v2 | ≥ 2.30.0&&< 2.32.7 | 2.32.7go get github.com/coder/coder/v2@v2.32.7 |
| 🐹Go | github.com/coder/coder/v2 | all versions | 2.29.17go get github.com/coder/coder/v2@v2.29.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coder/coder/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/coder/coder/v2 to 2.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h58c-xccx-75m3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-h58c-xccx-75m3 in your dependencies?
Find it across Go, including transitive dependencies.