Skip to main content
VulnerabilityPublished

CVE-2026-55438: V2 · Coder's workspace app CORS origin check can be bypassed via UUID-based subdomain spoofing

Affects github.com/coder/coder/v2Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.8 Medium : upgrade to 2.34.2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.34.2, 2.33.8, 2.32.7 +1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Gogithub.com/coder/coder/v2Affected
  • >=2.34.0 <2.34.2
Fixed in
  • 2.34.2
Gogithub.com/coder/coder/v2Affected
  • >=2.33.0 <2.33.8
Fixed in
  • 2.33.8
Gogithub.com/coder/coder/v2Affected
  • >=2.30.0 <2.32.7
Fixed in
  • 2.32.7
Gogithub.com/coder/coder/v2Affected
  • <2.29.17
Fixed in
  • 2.29.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Official patches are available and have been backported to all supported release lines: versions 2.34.2, 2.33.8, 2.32.7, and 2.29.17. Users should upgrade to these fixed versions to remediate the vulnerability. No workarounds are available. Applying the official fix fully mitigates the issue by validating the subdomain username against the actual workspace owner and enforcing correct CORS origin checks.

Description

### Summary 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. > **Note:** Practical exploitation requires subdomain app routing (wildcard hostname) enabled and a victim who visits the attacker's crafted app URL while authenticated. ### Impact An authenticated user could craft a subdomain encoding their own workspace UUID and a victim's username. If the victim visited the attacker's URL, the attacker's JavaScript could issue credentialed cross-origin `fetch()` requests to the victim's workspace apps and read the responses, exfiltrating data accessible through those apps. ### Patches The fix validates the subdomain username against the resolved workspace's actual owner and bases the same-owner CORS decision on the authoritative owner identity. The fix was backported to all supported release lines: | Release line | Patched version | |---|---| | 2.34 | [v2.34.2](https://github.com/coder/coder/releases/tag/v2.34.2) | | 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) | | 2.32 | [v2.32.7](https://github.com/coder/coder/releases/tag/v2.32.7) | | 2.29 (ESR) | [v2.29.17](https://github.com/coder/coder/releases/tag/v2.29.17) | ### Workarounds None. ### Resources - Fix: #26086, #26085 ### Credits Coder would like to thank Anthropic's Security Team (ANT-2026-22434) for independently disclosing this issue!

References

Community reviews

Loading reviews…