{"items":[{"id":"NVI-00017771","kind":"vulnerability","title":"Coder's AI Bridge Proxy skips TLS certificate verification in default configuration","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-84rm-42xw-mx52","CVE-2026-55436"],"plain_summary":"GitHub lists this reviewed advisory for github.com/coder/coder/v2, github.com/coder/coder/v2, github.com/coder/coder/v2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0982227a94cd239d1245ccac856cc408"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-06T21:12:05.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-607fa4cf2a573e0b890bca3e0cd0cfa2"},{"kind":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.258%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.17573. Missing scores are unknown.","source_id":"sr-0982227a94cd239d1245ccac856cc408"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-607fa4cf2a573e0b890bca3e0cd0cfa2","url":"https://github.com/advisories/GHSA-84rm-42xw-mx52","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-84rm-42xw-mx52","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:36:01.427Z"},{"id":"sr-0982227a94cd239d1245ccac856cc408","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55436","publisher":"FIRST EPSS","observed_at":"2026-11-06T07:17:46.386Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.34.0, < 2.34.2"]},{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.33.0, < 2.33.8"]},{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.30.0, < 2.32.7"]}],"null_published_at":"2026-11-08T15:11:49.414Z","source_updated_at":"2026-07-06T21:12:05.000Z","source_disclosed_at":"2026-07-06T21:12:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-04T23:36:01.427Z"},{"id":"NVI-00017771","kind":"vulnerability","title":"Coder's AI Bridge Proxy skips TLS certificate verification in default configuration","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-84rm-42xw-mx52","CVE-2026-55436"],"plain_summary":"GitHub lists this reviewed advisory for github.com/coder/coder/v2, github.com/coder/coder/v2, github.com/coder/coder/v2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-06T21:12:05.000Z","value":"7.4 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-607fa4cf2a573e0b890bca3e0cd0cfa2"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-607fa4cf2a573e0b890bca3e0cd0cfa2","url":"https://github.com/advisories/GHSA-84rm-42xw-mx52","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-84rm-42xw-mx52","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T23:36:01.427Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.34.0, < 2.34.2"]},{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.33.0, < 2.33.8"]},{"certainty":"source_listed","source_ids":["sr-607fa4cf2a573e0b890bca3e0cd0cfa2"],"technology":"github.com/coder/coder/v2","known_exclusions":[],"conditions_summary":"### Summary\n\nThe 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.\n\n> **Note:** 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.\n\n### Impact\n\nAn attacker positioned between the proxy and the Coder server, via ARP spoofing, DNS poisoning or control of proxy environment variables, could intercept injected Coder session tokens, user-supplied provider API keys (BYOK) and full request and response bodies including prompts and completions. The default transport also honored `HTTP_PROXY` and `HTTPS_PROXY`, allowing environment-based traffic redirection.\n\n### Patches\n\nThe fix applies the secure transport (TLS 1.2 or higher using system root CAs) unconditionally. The AI Bridge Proxy was introduced in v2.30.0. Earlier release lines including the v2.29 ESR line are not affected.\n\nThe fix","public_affected_ranges":[">= 2.30.0, < 2.32.7"]}],"null_published_at":"2026-11-05T19:10:21.466Z","source_updated_at":"2026-07-06T21:12:05.000Z","source_disclosed_at":"2026-07-06T21:12:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-04T23:36:01.427Z"}],"next_cursor":null,"snapshot_revision":"42594"}