CVE Intelligence
Medium Access control

CVE-2026-111928 — Coder 2.0.0 before 2.34.8 Authorization Bypass via User-Level ACL in RBAC Policy

Coder from 2.0.0 before 2.34.8 contains an incorrect authorization vulnerability in the acl_allow rule of coderd/rbac/policy.rego, which does not verify organization membership for per-user ACL entries, and organization member removal does not scrub those entries. Authenticated users removed from an organization can keep accessing previously granted org-scoped resources such as templates and workspaces via the API.

Published Oct 17, 2026 · Updated Oct 19, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.14%
ahead of 3% of scored CVEs · Oct 19, 2026
Affects
Coder
Coder
CVSS base
5.4
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Coder Coder).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Coder Coder ≥ 2.0.0 and < 2.34.8 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
5.3 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
5.4 CVSS 3.1 Medium 2.8 2.5 disclosure@vulncheck.com via NIST National Vulnerability Database
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.4 CVSS 3.1 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

EPSS over time FIRST

Oct 18, 2026 → Oct 19, 2026 · 2 reading(s) · max 0.14%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Audit administrative actions and access to resources outside each user’s normal pattern.
web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 19, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Published → Received
    Oct 17, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 17, 2026
  • Affected products added · coder/coder
    Oct 17, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 5.4
    Oct 17, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 17, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 17, 2026 · Alertas do Telegram
  • CVE published
    Oct 17, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 17, 2026 – Oct 19, 2026
  • 1× Official description updated · Oct 17, 2026 – Oct 17, 2026

References

4 on the record

Elsewhere on this site

Coder
every CVE for this vendor
Access control
same class
CWE-863
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-111934 Coder before 2.34.7 IP Spoofing via X-Forwarded-For Header 2d
  • CVE-2026-111933 Coder before 2.34.2 User Enumeration via Login Placeholder Hash 2d
  • CVE-2026-111932 Coder before 2.34.2 Stored HTML Injection via Appearance Settings 2d
  • CVE-2026-111931 Coder 2.0.0 before 2.34.8 Open Redirect via Workspace App Proxy 2d
  • CVE-2026-111927 Coder before 2.35.4 Credential Theft via Workspace Proxy Hostname Prefix Match 2d
  • CVE-2026-111926 Coder from 2.10.0 before 2.34.8 Information Disclosure via Agent /debug/manifest 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-111928 is "Coder 2.0.0 before 2.34.8 Authorization Bypass via User-Level ACL in RBAC Policy", rated Medium. It affects Coder (Coder); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.4 describes technical severity. EPSS 0.14% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.