# CVE-2026-111927 — coder

> As of 2026-10-17, CVE-2026-111927 is a HIGH-severity vulnerability in coder, CVSS v3.1 7.7, EPSS 0.2% (9.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-111927 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-111927?

Coder before 2.29.20, 2.33.0 before 2.33.12, 2.34.0 before 2.34.8, and 2.35.0 before 2.35.4 contains an improper hostname validation flaw in GetWorkspaceProxyByHostname whose SIMILAR TO pattern performs a prefix match, so any domain that is a string prefix of a workspace-proxy access URL is trusted as a proxy. Attackers owning such a domain can lure an authenticated victim to a crafted /api/v2/applications/auth-redirect link, capture the redirected application_connect API key, and replay it to access the victim's workspace apps.

The record classifies CVE-2026-111927 under weakness class [CWE-522](https://intel.threadlinqs.com/cwe/CWE-522). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs a user to take an action first, and has high impact on confidentiality, integrity. 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:** 7.7 — HIGH (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **CVSS v4.0 base score:** 8.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 9.7% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-17

## Is CVE-2026-111927 being exploited?

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

## Affected products and versions

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

## How to fix CVE-2026-111927

Vendor advisory: [https://github.com/coder/coder/security/advisories/GHSA-h58h-qvv5-xvwg](https://github.com/coder/coder/security/advisories/GHSA-h58h-qvv5-xvwg). 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-111927

No threat campaign in the Threadlinqs corpus currently references CVE-2026-111927, 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-h58h-qvv5-xvwg)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/coder-before-2.35.4-credential-theft-via-workspace-proxy-hostname-prefix-match)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-111927
No Threadlinqs detection currently covers CVE-2026-111927; 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