CVE-2026-55436

Coder's AI Bridge Proxy skips TLS certificate verification in default configuration

HIGH
7.4
CVSS Score
Published: July 8, 2026 at 12:26 AM UTC
Updated: July 8, 2026 at 07:55 PM UTC
1 product affected across 1 vendorCoder

Using coder by coder?

Get instant alerts when new vulnerabilities affect coder - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.30.0 and prior to versions 2.32.7, 2.33.8, and 2.34.2, the AI Bridge Proxy (`aibridgeproxyd`) created a goproxy server whose default transport set `InsecureSkipVerify: true` and only assigned a secure transport when an upstream proxy was configured. In the default configuration (no upstream proxy), outbound HTTPS to the Coder access URL accepted any TLS certificate. Practical exploitation requires an on-path (man-in-the-middle) position between the AI Bridge Proxy and the Coder server. Deployments where they are co-located over loopback are effectively unaffected. The fix in versions 2.32.7, 2.33.8, and 2.34.2 applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. As a workaround, ensure the Coder access URL uses a trusted certificate and secure the network path between the AI Bridge Proxy and the Coder server (for example, loopback or mTLS).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.32.7v < 2.33.8v < 2.34.22.30.0 ≤ v < 2.32.72.33.0 ≤ v < 2.33.82.34.0 ≤ v < 2.34.2
Affected range stops below 2.32.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.33.8, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.34.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (5)

x_refsource_CONFIRMPatchVendor Advisory
Source: cverecord
https://github.com/coder/coder/security/advisories/GHSA-84rm-42xw-mx52
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/coder/coder/pull/26131
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.32.7
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.33.8
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.34.2

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.4HIGHGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card