CVE-2026-55430

Coder's subdomain workspace app routing trusts unauthenticated X-Forwarded-Host header, enabling cross-app data access

MEDIUM
6.8
CVSS Score
Published: July 8, 2026 at 12:03 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
MEDIUM6.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the workspace app proxy resolves the target app from `httpapi.RequestHost()` which prefers the `X-Forwarded-Host` header over the real `Host` header. No middleware strips `X-Forwarded-Host` before routing and the header is not browser-forbidden so client-side JavaScript can set it on `fetch()` calls. Practical exploitation requires subdomain app routing (wildcard hostname) enabled, a victim who visits the attacker's shared app and a deployment whose upstream proxy does not strip `X-Forwarded-Host`. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 trusts `X-Forwarded-Host` only from configured trusted proxies and otherwise resolves the routing host from the verified request host. As a workaround, place an upstream reverse proxy that strips or overwrites `X-Forwarded-Host` on untrusted requests.

Affected

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

v < 2.29.17v < 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.29.17, so it looks safe — our inference, not a vendor statement
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 (6)

x_refsource_CONFIRMPatchVendor Advisory
Source: cverecord
https://github.com/coder/coder/security/advisories/GHSA-5g4w-3vw9-478w
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/coder/coder/pull/26204
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/coder/coder/releases/tag/v2.29.17
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 automatablePartial impact

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

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-345CWE-441

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