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… (CVE-2026-111933)
Description
Coder versions 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 have a user enumeration vulnerability. This occurs because the function userpassword.Compare() uses a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Attackers can exploit this by submitting logins with the password "hunter2" and observing different HTTP response codes (403 vs 401) to identify valid user accounts and reveal the authentication provider for SSO-only users. The vulnerability has a CVSS score of 3.7, indicating medium severity.
CVSS v3.1
Score 3.7low
Affected software
pkg:github/coder/coderRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Coder affects multiple version ranges prior to 2.29.17, 2.32.7, 2.33.8, and 2.34.2 respectively. It arises from the userpassword.Compare() function substituting a fixed placeholder hash based on the string "hunter2" when no stored password hash exists. This behavior allows unauthenticated attackers to submit login attempts with the password "hunter2" and differentiate HTTP 403 Forbidden responses from HTTP 401 Unauthorized responses. This difference enables attackers to enumerate valid user accounts and identify the authentication provider used by SSO-only users. The issue is classified under CWE-203 (Information Exposure Through Discrepancy).
Potential Impact
The vulnerability allows unauthenticated attackers to enumerate valid user accounts by distinguishing HTTP response codes during login attempts. This information disclosure can aid attackers in further targeted attacks or reconnaissance. The authentication provider of SSO-only users can also be revealed. The CVSS score of 3.7 reflects a low to medium impact primarily related to information disclosure without direct compromise of confidentiality, integrity, or availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, monitor for updates from the vendor and avoid exposing login endpoints unnecessarily. Do not rely on this mechanism for user enumeration protection. Implement additional rate limiting or anomaly detection to mitigate enumeration attempts if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wwfw-5crg-94f6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-111933"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6ad3f4c32cdf04f656656bb7
Added to database: 10/17/2026, 22:20:51 UTC
Last enriched: 10/17/2026, 22:28:33 UTC
Last updated: 10/17/2026, 23:08:10 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.