V2: Suspended Coder users retain access to AI Bridge LLM proxy endpoints (CVE-2026-55435)
### 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!
AI Analysis
Technical Summary
The AI Bridge proxy endpoints in Coder authenticate requests by validating key format, expiry, secret, and user status but omit checking if the user account is suspended. Because suspension does not revoke existing API keys, suspended users with unexpired tokens can continue accessing AI Bridge LLM proxy endpoints. This allows them to consume paid provider resources and invoke MCP tools if enabled. The vulnerability was introduced in version 2.30.0 and affects all subsequent versions until patched. Official fixes are available in versions 2.32.7, 2.33.8, and 2.34.2. The recommended workaround is to delete API keys of suspended users to prevent continued access.
Potential Impact
Suspended users with previously issued long-lived API tokens can continue to access AI Bridge LLM proxy endpoints, potentially consuming paid resources billed to the deployment and invoking injected MCP tools. This unauthorized access persists until the token expires or is deleted, which may be months after suspension. There is no direct impact on confidentiality or availability, but integrity and resource usage are affected.
Mitigation Recommendations
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.
V2: Suspended Coder users retain access to AI Bridge LLM proxy endpoints (CVE-2026-55435)
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!
CVSS v3.1
Score 5.4medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The AI Bridge proxy endpoints in Coder authenticate requests by validating key format, expiry, secret, and user status but omit checking if the user account is suspended. Because suspension does not revoke existing API keys, suspended users with unexpired tokens can continue accessing AI Bridge LLM proxy endpoints. This allows them to consume paid provider resources and invoke MCP tools if enabled. The vulnerability was introduced in version 2.30.0 and affects all subsequent versions until patched. Official fixes are available in versions 2.32.7, 2.33.8, and 2.34.2. The recommended workaround is to delete API keys of suspended users to prevent continued access.
Potential Impact
Suspended users with previously issued long-lived API tokens can continue to access AI Bridge LLM proxy endpoints, potentially consuming paid resources billed to the deployment and invoking injected MCP tools. This unauthorized access persists until the token expires or is deleted, which may be months after suspension. There is no direct impact on confidentiality or availability, but integrity and resource usage are affected.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wqxv-w64v-5wh6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-55435"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a4c340227e9c797195f5e65
Added to database: 07/06/2026, 23:02:26 UTC
Last enriched: 07/06/2026, 23:11:48 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.