github.com/coder/coder/v2
Affected
- introduced
2.34.0, fixed2.34.2(semver)
Fixed versions
2.34.2
Fix
- Fixed version
2.34.2go get github.com/coder/coder/[email protected]
Advisory
Also known as: CVE-2026-55437, GO-2026-5919
Coder vulnerable to stored HTML injection via workspace agent logs in AgentLogLine component
Summary
The AgentLogLine dashboard component instantiated ansi-to-html without escapeXML: true and inserted the result via dangerouslySetInnerHTML so HTML embedded in workspace agent log lines was rendered as live markup. Server-side sanitization did not neutralize HTML metacharacters.
> Note: Exploitation requires a victim to view attacker-controlled agent logs in the dashboard.
Impact
A user who could run a workspace could emit arbitrary HTML into agent logs; when another user, including an administrator, viewed the workspace page, it rendered in their session. Content Security Policy blocked inline scripts but an attacker could still inject a meta refresh redirect, style rules for UI redressing or CSS-based exfiltration or external img beacons. This required workspace-owner access and a victim viewing the page.
Patches
The fix enables escapeXML: true so HTML metacharacters are escaped before DOM insertion.
The fix was backported to all supported release lines:
| Release line | Patched version |
|---|---|
| 2.34 | v2.34.2 |
| 2.33 | v2.33.8 |
| 2.32 | v2.32.7 |
| 2.29 (ESR) | v2.29.17 |
Workarounds
None.
Resources
Credits
Coder would like to thank Anthropic's Security Team (ANT-2026-22449) for independently disclosing this issue!
Medium Basis: The source's own band: MODERATE
2.34.0, fixed 2.34.2 (semver)2.34.2
2.34.2go get github.com/coder/coder/[email protected]2.33.0, fixed 2.33.8 (semver)2.33.8
2.33.8go get github.com/coder/coder/[email protected]2.30.0, fixed 2.32.7 (semver)2.32.7
2.32.7go get github.com/coder/coder/[email protected]0, fixed 2.29.17 (semver)2.29.17
2.29.17go get github.com/coder/coder/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0