Advisory

GHSA-wqxv-w64v-5wh6

Also known as: CVE-2026-55435, GO-2026-5925

Summary

Suspended Coder users retain access to AI Bridge LLM proxy endpoints

Details

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 |
| 2.33 | v2.33.8 |
| 2.32 | 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!

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-06 21:11 UTC
Modified
2026-07-07 22:30 UTC

Affected packages and fixes

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.34.0, fixed 2.34.2 (semver)

Fixed versions

2.34.2

Fix

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.33.0, fixed 2.33.8 (semver)

Fixed versions

2.33.8

Fix

github.com/coder/coder/v2

Go · All systems

Affected

  • introduced 2.30.0, fixed 2.32.7 (semver)

Fixed versions

2.32.7

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences