Vulnerabilities

Vulnerability · CVE-2026-111933

Coder before 2.34.2 User Enumeration via Login Placeholder Hash

Published Aug 20, 2026 · catalog updated Oct 18, 2026 · Coder before 2.34.2 User

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-111933. A missing EPSS score is not a low risk. Compare Coder before 2.34.2 User with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Coder before 2.34.2 User).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium6.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Advisory link
Affected products
Go github.com/coder/coder · Go github.com/coder/coder/v2 · vendor coder coder

### Summary substituted a placeholder hash derived from the well-known string when the stored hash was empty. Submitting 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 , 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](https://github.com/coder/coder/releases/tag/v2.34.2) | | 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) | | 2.32 | [v2.32.7](https://github.com/coder/coder/releases/tag/v2.32.7) | | 2.29 (ESR) | [v2.29.17](https://github.com/coder/coder/releases/tag/v2.29.17) | ### Workarounds None. ### References - Fix: #26205 ### Credits We'd like to thank Anthropic's Security Team (ANT-2026-22433) for independently disclosing this issue!

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/coder/coderversion unspecified
  • Go github.com/coder/coder/v20 → 2.29.17
  • Go github.com/coder/coder/v22.30.0 → 2.32.7
  • Go github.com/coder/coder/v22.33.0 → 2.33.8
  • Go github.com/coder/coder/v22.34.0 → 2.34.2
  • vendor coder coderversion unspecified

How to fix CVE-2026-111933

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-111933. A missing EPSS score is not a low risk. Compare Coder before 2.34.2 User with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 2.29.17, 2.30.0 → 2.32.7, 2.33.0 → 2.33.8, 2.34.0 → 2.34.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-203: Observable Discrepancy; CWE-204. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 17, 2026 · NIST NVD

    Detected

    Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate vali

  2. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.34.2; github.com/coder/coder/v2 fixed in 2.33.8; github.com/coder/coder/v2 fixed in 2.32.7; github.com/coder/coder/v2 fixed in 2.29.17

  3. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.34.2

  4. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.33.8

  5. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.32.7

  6. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.29.17

  7. Oct 18, 2026 · Go Vulnerability Database

    Fix available

    github.com/coder/coder/v2 fixed in 2.29.17

  8. Oct 18, 2026 · Go Vulnerability Database

    Updated

    ### Summary substituted a placeholder hash derived from the well-known string when the stored hash was empty. Submitting 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

Sources

  • CVE.orgVulnerability recordCVE-2026-111933

    Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticat

    cve.org
  • Go Vulnerability DatabasePackage advisoryGHSA-8fxq-53rx-ph5f

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

    osv.dev
  • Go Vulnerability DatabasePackage advisoryGO-2026-6265

    Coder: Login endpoint user enumeration via timing-defense placeholder in password comparison in github.com/coder/coder

    osv.dev
  • NIST NVDVulnerability recordCVE-2026-111933

    Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticat

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.