# CVE-2026-111933 — coder

> As of 2026-10-17, CVE-2026-111933 is a LOW-severity vulnerability in coder, CVSS v3.1 3.7, EPSS 0.2% (12.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-111933 as of 2026-10-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-17

## What is CVE-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. 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.

The record classifies CVE-2026-111933 under weakness class [CWE-203](https://intel.threadlinqs.com/cwe/CWE-203). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 26 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.7 — LOW (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **CVSS v4.0 base score:** 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`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 12.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-17

## Is CVE-2026-111933 being exploited?

It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [coder](https://intel.threadlinqs.com/vendors/coder): coder

## How to fix CVE-2026-111933

Vendor advisory: [https://github.com/coder/coder/security/advisories/GHSA-8fxq-53rx-ph5f](https://github.com/coder/coder/security/advisories/GHSA-8fxq-53rx-ph5f). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-111933

No threat campaign in the Threadlinqs corpus currently references CVE-2026-111933, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, GitHub Security Advisories, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/coder/coder/security/advisories/GHSA-8fxq-53rx-ph5f)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/coder-before-2.34.2-user-enumeration-via-login-placeholder-hash)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-111933
No Threadlinqs detection currently covers CVE-2026-111933; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp