What is GHSA-8FXQ-53RX-PH5F?

GHSA-8FXQ-53RX-PH5F 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.

How severe is GHSA-8FXQ-53RX-PH5F?

GHSA-8FXQ-53RX-PH5F has a CVSS score of 3.7 (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.

Which versions of github.com/coder/coder/v2 are affected by GHSA-8FXQ-53RX-PH5F?

github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.

Is there a fix for GHSA-8FXQ-53RX-PH5F?

Yes. GHSA-8FXQ-53RX-PH5F is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.

Is GHSA-8FXQ-53RX-PH5F exploitable, and should I be worried?

Whether GHSA-8FXQ-53RX-PH5F 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.

What actually determines whether GHSA-8FXQ-53RX-PH5F 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.

How do I fix GHSA-8FXQ-53RX-PH5F?

Upgrade: github.com/coder/coder/v2 to 2.34.2 or later, github.com/coder/coder/v2 to 2.33.8 or later, github.com/coder/coder/v2 to 2.32.7 or later, github.com/coder/coder/v2 to 2.29.17 or later.

GHSA-8FXQ-53RX-PH5F in github.com/coder/coder/v2

Q: How severe is GHSA-8FXQ-53RX-PH5F?

GHSA-8FXQ-53RX-PH5F has a CVSS score of 3.7 (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.

Q: Which versions of github.com/coder/coder/v2 are affected by GHSA-8FXQ-53RX-PH5F?

github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.

Q: Is there a fix for GHSA-8FXQ-53RX-PH5F?

Yes. GHSA-8FXQ-53RX-PH5F is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.

Q: Is GHSA-8FXQ-53RX-PH5F exploitable, and should I be worried?

Whether GHSA-8FXQ-53RX-PH5F 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.

Q: What actually determines whether GHSA-8FXQ-53RX-PH5F 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.

Q: How do I fix GHSA-8FXQ-53RX-PH5F?

Upgrade: github.com/coder/coder/v2 to 2.34.2 or later, github.com/coder/coder/v2 to 2.33.8 or later, github.com/coder/coder/v2 to 2.32.7 or later, github.com/coder/coder/v2 to 2.29.17 or later.

Summary

Coder: Login endpoint user enumeration via timing-defense placeholder in password comparison

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.

Workarounds

None.

References

Fix: #26205

Credits

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

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.

GHSA-8FXQ-53RX-PH5F has a CVSS score of 3.7 (Low). 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 (2.34.2, 2.33.8, 2.32.7, 2.29.17); upgrading removes the vulnerable code path.

Affected versions

github.com/coder/coder/v2 (>= 2.34.0, < 2.34.2) github.com/coder/coder/v2 (>= 2.33.0, < 2.33.8) github.com/coder/coder/v2 (>= 2.30.0, < 2.32.7) github.com/coder/coder/v2 (< 2.29.17)

Security releases

github.com/coder/coder/v2 → 2.34.2 (go) github.com/coder/coder/v2 → 2.33.8 (go) github.com/coder/coder/v2 → 2.32.7 (go) github.com/coder/coder/v2 → 2.29.17 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is GHSA-8FXQ-53RX-PH5F? GHSA-8FXQ-53RX-PH5F 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.
How severe is GHSA-8FXQ-53RX-PH5F? GHSA-8FXQ-53RX-PH5F has a CVSS score of 3.7 (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.
Which versions of github.com/coder/coder/v2 are affected by GHSA-8FXQ-53RX-PH5F? github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.
Is there a fix for GHSA-8FXQ-53RX-PH5F? Yes. GHSA-8FXQ-53RX-PH5F is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.
Is GHSA-8FXQ-53RX-PH5F exploitable, and should I be worried? Whether GHSA-8FXQ-53RX-PH5F 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
What actually determines whether GHSA-8FXQ-53RX-PH5F 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.
How do I fix GHSA-8FXQ-53RX-PH5F?
- 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

CVE-IDSeverityPackage summary

GHSA-H58C-XCCX-75M3Lowgithub.com/coder/coder/v2: Coder: Stored HTML injection via unescaped ApplicationName and LogoURL appearance settings GHSA-QRWJ-VH9X-GW5VHighgithub.com/coder/coder/v2: Coder's workspace agent API insecure redirect handling allowed cross-agent file read and write CVE-2026-55438Mediumgithub.com/coder/coder/v2: Coder's workspace app CORS origin check can be bypassed via UUID-based subdomain spoofing CVE-2026-55437Mediumgithub.com/coder/coder/v2: Coder vulnerable to stored HTML injection via workspace agent logs in AgentLogLine component CVE-2026-55436Highgithub.com/coder/coder/v2: Coder's AI Bridge Proxy skips TLS certificate verification in default configuration