# CVE-2026-111933: Coder before 2.34.2 User Enumeration via Login Placeholder Hash > Unauthenticated attackers can enumerate valid user accounts and identify SSO-only users by exploiting a placeholder hash comparison flaw in the login mechanism. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Oct 2026 - **Updated:** 19 Oct 2026 - **Also known as:** GHSA-8fxq-53rx-ph5f, GHSA-wwfw-5crg-94f6, GO-2026-6265 ## What is CVE-2026-111933? CVE-2026-111933 is a medium-severity vulnerability in coder, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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 valid accounts and reveal the authentication provider of SSO-only users. Weakness: CWE-203 (Observable Discrepancy) ## Which versions are affected by CVE-2026-111933? 10 open source packages ship an affected version, including github.com/coder/coder/v2 and github.com/coder/coder. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17, 2.32.7, 2.33.8, 2.34.2 | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17 | | `github.com/coder/coder/v2` | Go | All versions | 2.29.17 | | `github.com/coder/coder/v2` | Go | From 2.30.0 | 2.32.7 | | `github.com/coder/coder/v2` | Go | From 2.30.0 | 2.32.7 | | `github.com/coder/coder/v2` | Go | From 2.33.0 | 2.33.8 | | `github.com/coder/coder/v2` | Go | From 2.33.0 | 2.33.8 | | `github.com/coder/coder/v2` | Go | From 2.34.0 | 2.34.2 | | `github.com/coder/coder/v2` | Go | From 2.34.0 | 2.34.2 | | `github.com/coder/coder` | Go | All versions | None | ## How do I fix CVE-2026-111933? Upgrade github.com/coder/coder/v2 to a fixed version for your release line: 2.29.17, 2.32.7, 2.33.8 or 2.34.2. ## Is CVE-2026-111933 being exploited? There is no known exploitation of CVE-2026-111933 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-111933 and fix it if it is affected. What it is: CVE-2026-111933 is a medium-severity vulnerability in coder, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-111933 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17, 2.32.7, 2.33.8, 2.34.2 - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17 - github.com/coder/coder/v2 (Go): affected all versions; fixed in 2.29.17 - github.com/coder/coder/v2 (Go): affected from 2.30.0; fixed in 2.32.7 - github.com/coder/coder/v2 (Go): affected from 2.30.0; fixed in 2.32.7 - github.com/coder/coder/v2 (Go): affected from 2.33.0; fixed in 2.33.8 - github.com/coder/coder/v2 (Go): affected from 2.33.0; fixed in 2.33.8 - github.com/coder/coder/v2 (Go): affected from 2.34.0; fixed in 2.34.2 - github.com/coder/coder/v2 (Go): affected from 2.34.0; fixed in 2.34.2 - github.com/coder/coder (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-111933/ (Markdown: https://insights.sbomify.com/CVE-2026-111933/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111933 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111933 - OSV: https://osv.dev/vulnerability/CVE-2026-111933 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-111933/ Summaries are generated and may contain mistakes; the official description above is the record.