Skip to main content
VulnerabilityPublished Updated

CVE-2026-55435: V2 · Suspended Coder users retain access to AI Bridge LLM proxy endpoints

Affects github.com/coder/coder/v2Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.34.2 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.34.2, 2.33.8, 2.32.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade github.com/coder/coder/v2 to 2.34.2; github.com/coder/coder/v2 to 2.33.8; github.com/coder/coder/v2 to 2.32.7.

Affected software

ProductAffectedFixed in
Gogithub.com/coder/coder/v2Affected
  • >=2.34.0 <2.34.2
Fixed in
  • 2.34.2
Gogithub.com/coder/coder/v2Affected
  • >=2.33.0 <2.33.8
Fixed in
  • 2.33.8
Gogithub.com/coder/coder/v2Affected
  • >=2.30.0 <2.32.7
Fixed in
  • 2.32.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Coder versions 2.32.7, 2.33.8, and 2.34.2 that updates AI Bridge authorization to reject non-active (suspended) users. Deployments should upgrade to these versions to remediate the issue. As a workaround, administrators should delete API keys of suspended users using the DELETE /api/v2/users/{user}/keys endpoint to immediately revoke access until the patch is applied.

Description

### Summary AI Bridge proxy endpoints authenticate via `Server.IsAuthorized` in `coderd/aibridgedserver`, which validates key format, expiry, secret and deleted or system users but does not check whether the account is suspended. Because suspension does not revoke existing API keys, a suspended user's unexpired token keeps working. > **Note:** Practical impact is limited to already-issued API keys of suspended users until those keys are deleted. ### Impact A suspended user with a previously issued long-lived token could continue calling AI Bridge LLM proxy endpoints, consuming paid provider resources billed to the deployment and, if injected MCP tools are enabled, invoking those tools. Access persists until the token expires, which may be months after suspension. ### Patches The fix makes AI Bridge authorization reject non-active users like the standard API key middleware. AI Bridge was introduced in v2.30.0. The v2.29 ESR line is not affected. The fix is available in the following releases: | Release line | Patched version | |---|---| | 2.34 | [v2.34.2](https://github.com/coder/coder/releases/tag/v2.34.2) | | 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) | | 2.32 | [v2.32.7](https://github.com/coder/coder/releases/tag/v2.32.7) | ### Workarounds On suspension, delete the user's API keys via `DELETE /api/v2/users/{user}/keys`. ### Resources - Fix: #26173 ### Credits Coder would like to thank Anthropic's Security Team (ANT-2026-22446) for independently disclosing this issue!

References

Community reviews

Loading reviews…