coder Workspace App Proxy up to 2.29.16/2.32.6/2.33.7/2.34.1 cross-domain policy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 1.73+ |
Summary
A vulnerability identified as problematic has been detected in coder Workspace App Proxy up to 2.29.16/2.32.6/2.33.7/2.34.1. This affects an unknown part. The manipulation leads to cross-domain policy. This vulnerability is listed as CVE-2026-55438. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in coder Workspace App Proxy up to 2.29.16/2.32.6/2.33.7/2.34.1 and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a cross-domain policy vulnerability. Using CWE to declare the problem leads to CWE-942. The product uses a cross-domain policy file that includes domains that should not be trusted. Impacted is confidentiality. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-55438 since 06/16/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 2.29.17, 2.32.7, 2.33.8 or 2.34.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-42151). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 2.29.0
- 2.29.1
- 2.29.2
- 2.29.3
- 2.29.4
- 2.29.5
- 2.29.6
- 2.29.7
- 2.29.8
- 2.29.9
- 2.29.10
- 2.29.11
- 2.29.12
- 2.29.13
- 2.29.14
- 2.29.15
- 2.29.16
- 2.32.0
- 2.32.1
- 2.32.2
- 2.32.3
- 2.32.4
- 2.32.5
- 2.32.6
- 2.33.0
- 2.33.1
- 2.33.2
- 2.33.3
- 2.33.4
- 2.33.5
- 2.33.6
- 2.33.7
- 2.34.0
- 2.34.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross-domain policyCWE: CWE-942 / CWE-346 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Workspace App Proxy 2.29.17/2.32.7/2.33.8/2.34.2
Timeline
06/16/2026 CVE reserved07/08/2026 Advisory disclosed
07/08/2026 VulDB entry created
07/08/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-55438 (🔒)
GCVE (CVE): GCVE-0-2026-55438
GCVE (VulDB): GCVE-100-376763
EUVD: 🔒
Entry
Created: 07/08/2026 03:24Updated: 07/08/2026 05:13
Changes: 07/08/2026 03:24 (53), 07/08/2026 05:13 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.