The flaw in coder:coder originates from the Server.IsAuthorized function that verifies key format, expiry, secret, and deletion or system status but neglects to check whether the account is suspended. As a result, a suspended user whose API key remains unexpired continues to be accepted by the AI Bridge proxy endpoints. The primary effect is that the suspended user can keep invoking the AI Bridge LLM service until the key is revoked or expires; this does not grant arbitrary code execution or additional data exfiltration beyond normal service use. The weakness is a classic broken access control (CWE‑863).

This issue affects the coder:coder product. Versions from 2.30.0 through 2.32.6, 2.33.7, and 2.34.1 are impacted. The vendor released patched versions 2.32.7, 2.33.8, and 2.34.2 that add the missing suspension check during authentication. Organizations using any of the affected releases should immediately upgrade to a patched version to eliminate the flaw.

The CVSS score of 5.4 indicates moderate severity, while the EPSS score of less than 1% suggests a very low probability of exploitation at present. The vulnerability is not listed in CISA’s KEV catalog, implying no documented widespread exploitation. An attacker would need possession of a suspended user’s still‑valid API key to exploit the weakness. Because the key can be intercepted or leaked, the inferred attack vector involves acquiring a suspended user’s remaining valid API key—through misconfigurations, logging, insider activity, or interception. With such a key, the attacker can continue to call the AI Bridge endpoints until the key is deleted or expires. The flaw is mitigated by enforcing suspension checks during authorization.