Quick answers
- Is CVE-2026-111928 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111928 being exploited in the wild.
- How severe is CVE-2026-111928?
- Medium severity, with a CVSS score of 5.4, published 17 October 2026.
- Which products and versions are affected?
- Coder 2.0.0 before 2.34.8.
- Is there a fix for CVE-2026-111928?
- Yes: fixed in 2.34.8, 2.35.0, 2.36.0. Until then: Administrators can immediately mitigate this issue by manually revoking user-level ACL entries on organization-scoped resources before removing a user from an organization. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111928 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111928?
- Check whether you run Coder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.34.8, 2.35.0, 2.36.0
Administrators can immediately mitigate this issue by manually revoking user-level ACL entries on organization-scoped resources before removing a user from an organization.
Technical details
The RBAC policy engine in coderd/rbac/policy.rego fails to verify current organization membership when evaluating user-level ACL entries on organization-scoped resources, unlike the corresponding group-level ACL rule which performs this check. Additionally, removing a member from an organization does not delete stale per-user ACL entries they held on org-scoped resources. An authenticated attacker (user who was previously in the organization) can exploit this by calling the API with a stale user-level ACL entry to access templates and workspaces after removal from the organization.
Affected products
- Coder Coder 2.0.0 before 2.34.8
Timeline
- 2026-08-10: disclosed
- 2026-10-17: advisory