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).
Published: 2026-07-08
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The AI Bridge Proxy component of Coder was incorrectly configured to skip TLS certificate verification when no upstream proxy was defined. This means that outbound HTTPS traffic to the Coder access URL would accept any certificate. An attacker who can position themselves on the network path between the Proxy and the Coder or reading payloads. The flaw is a classic TLS endpoint spoofing weakness (CWE‑295) that compromises confidentiality and integrity of data.

Affected Systems

This vulnerability affects Coder versions 2.30.0 through 2.32.6, 2.33.0 through 2.33.7, and 2.34.0 through 2.34.1. The issue is fixed in releases 2.32.7, 2.33.8, and 2.34.2 and later.

Risk and Exploitability

The CVSS score of 7.4 classifies the issue as high‑severity. The EPSS score of <1% indicates a very low but nonzero probability of exploitation, and the vulnerability is not listed in the C, suggesting no publicly known active exploit. The primary vector requires an on‑path position between the AI Bridge Proxy and the Coder server. Mitigation is achieved by upgrading to the fixed releases or by ensuring that the Coder access URL presents a trusted certificate and that the communication path is isolated, e.g., via loopback or mutual TLS.

Generated by OpenCVE AI on July 26, 2026 at 18:35 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Coder to a fixed release (v2.32.7, v2.33.8, or v2.34.2) or later, which enforces secure TLS transport unconditionally.
  • If an immediate upgrade is not possible, enforce the use of a trusted SSL certificate for the Coder access URL and limit the network path between the AI Bridge Proxy and the Coder mutual TLS).
  • When operating behind an upstream proxy, configure the proxy to perform its own certificate verification rather than relying on the AI Bridge Proxy’s insecure default.

Generated by OpenCVE AI on July 26, 2026 at 18:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-84rm-42xw-mx52 Coder's AI Bridge Proxy skips TLS certificate verification in default configuration
History

Wed, 08 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Wed, 08 Jul 2026 02:45:00 +0000

Type Values Removed Values Added
First Time appeared Coder
Coder coder
Vendors & Products Coder
Coder coder

Wed, 08 Jul 2026 01:00:00 +0000

Type Values Removed Values Added
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).
Title Coder's AI Bridge Proxy skips TLS certificate verification in default configuration
Weaknesses CWE-295
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-08T13:11:46.877Z

Reserved: 2026-06-16T21:59:57.017Z

Link: CVE-2026-55436

cve-icon Vulnrichment

Updated: 2026-07-08T13:11:43.652Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-26T18:45:03Z

Weaknesses
  • CWE-295

    Improper Certificate Validation