# CVE-2026-111931: Coder 2.0.0 before 2.34.8 Open Redirect via Workspace App Proxy

> Attackers can redirect users to malicious sites via crafted links on trusted subdomains, facilitating phishing attacks against Coder users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-98qx-9p2x-c4wh, GHSA-gp67-53hr-2cf4

## What is CVE-2026-111931?

CVE-2026-111931 is a medium-severity vulnerability in coder, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-111931?


## How do I fix CVE-2026-111931?

No fix has been published for CVE-2026-111931 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111931 being exploited?

There is no known exploitation of CVE-2026-111931 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111931 and fix it if it is affected.

What it is: CVE-2026-111931 is a medium-severity vulnerability in coder, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-111931 in the wild and no public exploit code.

Affected product: coder. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111931/ (Markdown: https://insights.sbomify.com/CVE-2026-111931/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111931
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111931
- OSV: https://osv.dev/vulnerability/CVE-2026-111931

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111931/
Summaries are generated and may contain mistakes; the official description above is the record.