Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111928 Overview
CVE-2026-111928 is an incorrect authorization vulnerability in Coder, affecting versions 2.0.0 through 2.34.7. The flaw resides in the acl_allow rule of coderd/rbac/policy.rego, which fails to verify organization membership for per-user Access Control List (ACL) entries. When an administrator removes a user from an organization, the system does not scrub the user's existing per-user ACL grants. The removed user retains API access to org-scoped resources such as templates and workspaces. The vulnerability is categorized under CWE-863: Incorrect Authorization.
Critical Impact
Authenticated users removed from a Coder organization continue to access templates and workspaces they were previously granted, bypassing organization-level access revocation.
Affected Products
- Coder versions 2.0.0 through 2.34.7
- Coder coderd RBAC policy module (coderd/rbac/policy.rego)
- Deployments relying on per-user ACL entries for org-scoped resources
Discovery Timeline
- 2026-10-17 - CVE-2026-111928 published to the National Vulnerability Database
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111928
Vulnerability Analysis
Coder uses Open Policy Agent (OPA) Rego policies to evaluate authorization decisions. The acl_allow rule in coderd/rbac/policy.rego evaluates whether a user holds a direct ACL grant on a resource. The rule checks for a matching user entry in the resource ACL but does not re-validate that the user still belongs to the organization owning the resource.
When an administrator removes a user from an organization, Coder deletes the user's organization role assignments. However, per-user ACL entries attached to individual templates and workspaces are not cleared. The stale ACL grants remain authoritative inside acl_allow, producing an authorization decision that permits continued API access.
The vulnerability allows read and write operations against previously accessible org-scoped resources through the Coder API. The impact is bounded to resources where the removed user previously held an explicit per-user ACL entry.
Root Cause
The root cause is a missing membership check inside the acl_allow policy rule. Authorization logic treats the ACL entry as a self-contained grant rather than a derived permission that depends on current organization membership. The user removal workflow compounds the issue by failing to scrub per-user ACL entries from org-scoped objects.
Attack Vector
Exploitation requires valid authenticated credentials for an account that previously belonged to a Coder organization and held per-user ACL grants. After removal from the organization, the attacker issues authenticated API requests to the previously accessible templates or workspaces. The server evaluates acl_allow, matches the stale ACL entry, and returns the resource.
No special tooling is required. Standard Coder API clients or curl against the authenticated REST endpoints are sufficient to demonstrate the bypass. See the GitHub Security Advisory GHSA-7v78-w67v-pm2g and the VulnCheck Advisory on Coder ACL Vulnerability for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-111928
Indicators of Compromise
- API audit log entries showing successful access to org-scoped templates or workspaces by user accounts no longer listed as members of the owning organization.
- Authentication events from users whose organization membership was recently revoked but who continue making authorized requests to coderd endpoints.
- ACL grants on templates and workspaces referencing user IDs that no longer appear in the organization membership tables.
Detection Strategies
- Correlate organization membership change events with subsequent API access against resources owned by that organization.
- Query the Coder database for per-user ACL entries on org-scoped resources and cross-reference against the current organization member list to identify stale grants.
- Enable verbose RBAC decision logging in coderd and alert when acl_allow grants access to a user without a matching organization role.
Monitoring Recommendations
- Monitor the Coder API audit log for access to templates and workspaces by recently removed users.
- Review access patterns to org-scoped resources after any organization membership change.
- Track changes to coderd/rbac/policy.rego and surrounding RBAC code to confirm the fixed policy is deployed.
How to Mitigate CVE-2026-111928
Immediate Actions Required
- Upgrade Coder to version 2.34.8 or later, which contains the corrected acl_allow policy and membership scrubbing logic.
- Audit all templates and workspaces for per-user ACL entries referencing accounts no longer in the owning organization, and remove them.
- Rotate API tokens for any accounts recently removed from an organization to invalidate active sessions.
Patch Information
The vendor fix is included in Coder 2.34.8. The patch updates the acl_allow rule in coderd/rbac/policy.rego to require current organization membership before honoring a per-user ACL grant, and updates the organization removal workflow to scrub per-user ACL entries. Refer to the GitHub Security Advisory GHSA-7v78-w67v-pm2g for release details.
Workarounds
- Manually delete per-user ACL entries for a user on all org-scoped resources immediately after removing that user from an organization.
- Prefer group-based ACL grants over per-user grants so that removal from an organization-linked group revokes access cleanly.
- Restrict administrative API access to known IP ranges to limit abuse opportunities until the patch is applied.
# Configuration example: upgrade Coder to the fixed release
coder server --version
# Upgrade via your package manager or container tag
docker pull ghcr.io/coder/coder:v2.34.8
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

