Coder cross-site request forgery bypass in middleware
Affects Coder 2.6.0 to before 2.29.26, 2.30.0 to before 2.34.18, 2.35.0 to before 2.37.10, and 2.38.0 to before 2.38.6. Fixed in 2.29.26, 2.34.18, 2.37.10, and 2.38.6.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.38.6, 2.37.10, 2.34.18, 2.29.26, 2.37.0
- Who is exposed
- Specific setups only
Summary
Written by a model
Coder 2.6.0 before 2.29.26, 2.30.0 before 2.34.18, 2.35.0 before 2.37.10, and 2.38.0 before 2.38.6 contains a cross-site request forgery vulnerability because CSRF exemption patterns in coderd/httpmw/csrf.go are matched as unanchored regular expressions, letting affected API routes skip CSRF token and same-origin checks. Attackers controlling a page same-site with the deployment can make signed-in users' browsers send forged POST requests that recreate dev containers or add users whose names contain derp to organizations.
Who should check
Teams running Coder 2.6.0 through 2.38.5 (affected release lines) where users sign in and open workspace apps or shared ports on the Coder access URL domain.
“Coder 2.6.0 before 2.29.26, 2.30.0 before 2.34.18, 2.35.0 before 2.37.10, and 2.38.0 before 2.38.6”
What to do
Check whether your setup matches what the bug needs.
Coder deployments running affected versions: 2.6.0 to before 2.29.26, 2.30.0 to before 2.34.18, 2.35.0 to before 2.37.10, or 2.38.0 to before 2.38.6.Upgrade to a fixed version: 2.38.6, 2.37.10, 2.34.18, 2.29.26, 2.37.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134362 (Coder from 2.38.0 before 2.38.6 CSRF Bypass via Unanchored Exemption Patterns), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134362 (entry last updated 2026-11-21):
Affected:
- Go package github.com/coder/coder/v2: from 2.38.0, fixed in 2.38.6
- Go package github.com/coder/coder/v2: from 2.37.0, fixed in 2.37.10
- Go package github.com/coder/coder/v2: from 2.30.0, fixed in 2.34.18
- Go package github.com/coder/coder/v2: from 2.6.0, fixed in 2.29.26
- Go package github.com/coder/coder/v2: from 2.35.0, fixed in 2.37.0
Fixed versions: 2.38.6, 2.37.10, 2.34.18, 2.29.26, 2.37.0.
Conditions (all must be true for the bug to be hit):
- Coder deployments running affected versions: 2.6.0 to before 2.29.26, 2.30.0 to before 2.34.18, 2.35.0 to before 2.37.10, or 2.38.0 to before 2.38.6. (source: https://www.vulncheck.com/advisories/coder-from-2.38.0-before-2.38.6-csrf-bypass-via-unanchored-exemption-patterns)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-134362 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134362 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/coder/coder/security/advisories/GHSA-jvgx-787p-cfmg
- https://www.vulncheck.com/advisories/coder-from-2.38.0-before-2.38.6-csrf-bypass-via-unanchored-exemption-patterns
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134362
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134362"}.Affected versions
- github.com/coder/coder/v2From 2.38.0 · fixed in 2.38.6Fixed in v2.38.6 (released Nov 3, 2026, 18 days before disclosure).
- github.com/coder/coder/v2From 2.37.0 · fixed in 2.37.10Fixed in v2.37.10 (released Nov 3, 2026, 18 days before disclosure).
- github.com/coder/coder/v2From 2.30.0 · fixed in 2.34.18Fixed in v2.34.18 (released Nov 3, 2026, 18 days before disclosure).
- github.com/coder/coder/v2From 2.6.0 · fixed in 2.29.26Fixed in v2.29.26 (released Nov 3, 2026, 18 days before disclosure).
- github.com/coder/coder/v2From 2.35.0 · fixed in 2.37.0The latest release, v2.39.1, is not affected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach10/20Affects Go packages
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · coder/coder · Advisory GHSA-jvgx-787p-cfmg |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134362 |
| Record | NVD · CVE-2026-134362 |
| Other links 1 | |
| Link | vulncheck.com · advisories/coder-from-2.38.0-before-2.38.6-csrf-bypass-via-unanchored-exemption-patterns |
Questions about CVE-2026-134362
Is CVE-2026-134362 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Coder's CSRF protection skips checks on some routes, but the exemption patterns were not anchored, so forged POST requests could reach exempt routes. An attacker could make a signed-in user's browser send such requests, such as recreating the user's dev container or adding a user whose name contains derp to an organization.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134362?
github.com/coder/coder/v2 (Go): from 2.38.0 before 2.38.6. github.com/coder/coder/v2 (Go): from 2.37.0 before 2.37.10. github.com/coder/coder/v2 (Go): from 2.30.0 before 2.34.18. github.com/coder/coder/v2 (Go): from 2.6.0 before 2.29.26. github.com/coder/coder/v2 (Go): from 2.35.0 before 2.37.0.
Source: cve.now feed data
Am I affected, and how do I check?
Coder deployments on 2.6.0 to before 2.29.26, 2.30.0 to before 2.34.18, 2.35.0 to before 2.37.10, or 2.38.0 to before 2.38.6 are in the affected ranges. Compare the installed Coder version against these ranges to check.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134362?
Upgrade to the fixed release for your branch: 2.29.26, 2.34.18, 2.37.10, or 2.38.6.
Source: vulncheck.com, github.com
Related
- CVE-2026-126308Coder 2.38.0 before 2.38.2 Session Token Leak via Sub-Agent External Apps
- CVE-2026-55429Coder's workspace app upsert allows cross-workspace agent rebinding via user-controlled app ID
- CVE-2026-126403Coder 2.38.0 before 2.38.4 Authorization Bypass via External Agent Credentials Endpoint
- CVE-2026-63443Coder: Workspace agent API insecure redirect handling allowed cross-agent file read and write
- CVE-2026-55431Coder's session token leaked to arbitrary hosts via `coder open app` for external workspace apps
- CVE-2026-126404Coder from 2.38.0 before 2.38.4 Privilege Escalation via API Key Creation
No corrections so far. Something wrong on this page? Report an error.