Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ GHSA-qrwj-vh9x-gw5v — coder

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-863 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Coder's workspace agent API insecure redirect handling allowed cross-agent file read and write

Summary

agentConn.apiClient() used the default redirect behavior of http.Client while its custom transport dialed the host from the request URL as long as the port was the workspace agent HTTP API port (4). Agent tailnet IPs are deterministic from agent UUIDs, so a malicious workspace agent could return a redirect to another agent's tailnet IP and cause the control-plane client to send the follow-up workspace agent API request to the victim agent instead of the intended agent.

Redirects that preserve the method and body, such as HTTP 307 and 308, allow replay of write and process-start requests. HTTP 301, 302 and 303 redirects only convert POST requests to GET requests, so they are sufficient to demonstrate redirected reads but not write or command-execution primitives.

Impact

An authenticated user with a running workspace and control of a modified workspace agent can redirect workspace agent API requests made to their agent toward another online workspace agent reachable on the tailnet. If the attacker knows the victim agent UUID, they can derive the victim's tailnet IP and target the victim's file APIs to read or write files as the victim workspace user.

In affected versions that expose the workspace agent process API, the same primitive can be chained to command execution as the victim workspace user by writing a payload through the redirected file API and then redirecting a process-start request to execute it. This crosses workspace and tenant boundaries.

Patches

The fix disables automatic redirect following for workspace agent API clients and pins all workspace agent API dials to the intended agent's deterministic tailnet address. Requests whose URL host does not match the intended agent are rejected instead of being dialed.

The fix was backported to all supported release lines:

| Release line | Patched version |

|---|---|

| 2.34 | [v2.34.4](https://github.com/coder/coder/releases/tag/v2.34.4) |

| 2.33 | [v2.33.10](https://github.com/coder/coder/releases/tag/v2.33.10) |

| 2.32 | [v2.32.9](https://github.com/coder/coder/releases/tag/v2.32.9) |

| 2.29 (ESR) | [v2.29.19](https://github.com/coder/coder/releases/tag/v2.29.19) |

Workarounds

None. Upgrading is required.

Resources

  • Fix: #26600

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability low.

Weakness class

GHSA-qrwj-vh9x-gw5v is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

GHSA-qrwj-vh9x-gw5v is recorded against 1 package.

  • github.com/coder/coder/v2

Timeline and source

Published on 6 July 2026 and last revised on 7 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Package)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
CWE CWE-863
Public Exploit ✅ No
Source OSV
Published 2026-07-06
Updated 2026-08-20
Modified 2026-07-07
Fix URL N/A

Affected Packages

Software From version Fixed in
github.com/coder/coder/v2

Similar Threats

Site Security Check

Is coder part of your stack?

GHSA-qrwj-vh9x-gw5v is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.