# CVE-2026-111930: Coder from 2.26.0 before 2.34.8 Information Disclosure via Workspace ACL Endpoint

> Authenticated users with workspace access can exploit an authorization flaw to harvest sensitive group member data via the ACL endpoint.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-cvrm-2xxr-hpcv, GHSA-jc76-qvj4-2385

## What is CVE-2026-111930?

CVE-2026-111930 is a medium-severity vulnerability in coder, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coder from 2.26.0 before 2.34.8 contains an incorrect authorization flaw in the GET /api/v2/workspaces/{id}/acl endpoint, which checks only workspace read access and then fetches group members using an elevated system context. Authenticated users granted workspace use access can query the endpoint to harvest group members' emails, login types, status, and last-seen and creation timestamps.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-111930 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111930 is a medium-severity vulnerability in coder, published on 17 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111930 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-111930/ (Markdown: https://insights.sbomify.com/CVE-2026-111930/index.md)
```

## Sources

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

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