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-111933, GO-2026-6265
Coder: Login endpoint user enumeration via timing-defense placeholder in password comparison
Summary
userpassword.Compare() substituted a placeholder hash derived from the well-known string "hunter2" when the stored hash was empty. Submitting "hunter2" therefore matched accounts with no password hash (nonexistent users and SSO-only users) and a subsequent login-type check returned an HTTP 403 that disclosed the account's login type, versus 401 for password users.
> Note: Practical exploitation is limited because the timing side channel is noisy and only reveals whether an account exists.
Impact
An unauthenticated attacker could enumerate valid accounts and their authentication provider by submitting logins with the password "hunter2", distinguishing nonexistent users, SSO users (provider revealed) and password users from the response. This aids credential-stuffing and targeted phishing. No authentication bypass or data access resulted.
Patches
The fix derives the timing-defense placeholder from a secure random value that no supplied password can match.
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.
References
Credits
We'd like to thank Anthropic's Security Team (ANT-2026-22433) for independently disclosing this issue!
Low Basis: The source's own band: LOW
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