Approved changes feed: RSS · Atom
cpe:2.3:a:coder:coder:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Coder (84d1e054-8332-5cb6-80cf-d3132582713f) |
|---|---|
| Product | Coder (0e5bc4c2-a12d-5571-9de8-d6e5010cec96) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-55438 |
vulnerable | 2026-07-29 01:00:28.461889 |
Coder's workspace app CORS origin check can be bypassed via UUID-based subdomain spoofing
MEDIUM (5.8)
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2, Coder's subdomain-based workspace app proxy allowed the same-owner CORS check to be bypassed. When a workspace-name subdomain segment parsed as a UUID, the workspace was resolved by ID without confirming the URL's username matched the real owner, while the CORS middleware trusted the unverified username in the hostname. Practical exploitation requires subdomain app routing (wildcard hostname) enabled and a victim who visits the attacker's crafted app URL while authenticated. The fix in versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2 validates the subdomain username against the resolved workspace's actual owner and bases the same-owner CORS decision on the authoritative owner identity. No known workarounds are available.
Published: 2026-07-08T00:31:20.573Z
Updated: 2026-07-08T17:10:30.943Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55437 |
vulnerable | 2026-07-29 01:00:28.461734 |
Coder vulnerable to stored HTML injection via workspace agent logs in AgentLogLine component
MEDIUM (5.4)
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2, the `AgentLogLine` dashboard component instantiated `ansi-to-html` without `escapeXML: true` and inserted the result via `dangerouslySetInnerHTML` so HTML embedded in workspace agent log lines was rendered as live markup. Server-side sanitization did not neutralize HTML metacharacters. Exploitation requires a victim to view attacker-controlled agent logs in the dashboard. The fix in versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2 enables `escapeXML: true` so HTML metacharacters are escaped before DOM insertion. No known workarounds are available.
Published: 2026-07-08T00:29:18.268Z
Updated: 2026-07-08T14:00:43.204Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55436 |
vulnerable | 2026-07-29 01:00:28.461584 |
Coder's AI Bridge Proxy skips TLS certificate verification in default configuration
HIGH (7.4)
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-08T00:26:13.175Z
Updated: 2026-07-08T13:11:46.877Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55435 |
vulnerable | 2026-07-29 01:00:28.461431 |
Suspended Coder users retain access to AI Bridge LLM proxy endpoints
MEDIUM (5.4)
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, 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. Practical impact is limited to already-issued API keys of suspended users until those keys are deleted. Versions 2.32.7, 2.33.8, and 2.34.2 patch the issue. As a workaround, on suspension, delete the user's API keys via `DELETE /api/v2/users/{user}/keys`.
Published: 2026-07-07T17:37:31.211Z
Updated: 2026-07-09T14:42:41.115Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55434 |
vulnerable | 2026-07-29 01:00:28.461207 |
Coder vulnerable to denial of service via unbounded request body in AI Bridge provider endpoints
MEDIUM (6.5)
Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.33.0 and prior to versions 2.33.8 and 2.34.2, AI Bridge provider handlers read request bodies with `io.ReadAll` without a maximum size so an authenticated user with AI Bridge access could send an arbitrarily large body and exhaust memory. Exploitation requires authenticated access to the AI Bridge endpoints and the impact is limited to availability (denial of service). Versions 2.33.8 and 2.34.2 patch the issue. No known workarounds are available.
Published: 2026-07-07T20:14:00.531Z
Updated: 2026-07-08T14:15:15.446Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55433 |
vulnerable | 2026-07-29 01:00:28.460990 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55432 |
vulnerable | 2026-07-29 01:00:28.460839 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55431 |
vulnerable | 2026-07-29 01:00:28.460682 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55430 |
vulnerable | 2026-07-29 01:00:28.460434 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55429 |
vulnerable | 2026-07-29 01:00:28.460183 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55428 |
vulnerable | 2026-07-29 01:00:28.460027 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55427 |
vulnerable | 2026-07-29 01:00:28.459859 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55079 |
vulnerable | 2026-07-29 01:00:28.321035 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55078 |
vulnerable | 2026-07-29 01:00:28.320764 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55077 |
vulnerable | 2026-07-29 01:00:28.320465 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55076 |
vulnerable | 2026-07-29 01:00:28.320183 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-55075 |
vulnerable | 2026-07-29 01:00:28.319679 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-46354 |
vulnerable | 2026-07-29 00:54:58.841141 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-45796 |
vulnerable | 2026-07-29 00:54:58.550550 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-44454 |
vulnerable | 2026-07-29 00:52:14.365695 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66411 |
vulnerable | 2026-06-08 07:41:18.887316 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-58437 |
vulnerable | 2026-06-08 07:35:18.275666 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-27918 |
vulnerable | 2026-06-08 06:33:25.064052 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.