Skip to main content

CVE-2026-134362coder cross-site request forgery

Low priorityLow2.3EPSS not scored yet

CVE-2026-134362 is a cross-site request forgery in coder, rated low (2.3 on CVSS 4.0).

Why this priority: Low severity, with no exploitation signal.

Published · Updated · NVD status: Awaiting Analysis

What it is

Another site can make a signed-in user's browser send a request the user never meant to send.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker act inside a signed-in user's browser session.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade coder to a fixed version for your release line (2.38.6, 2.37.10, 2.34.18).
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Web front ends and single-page apps. The flaw sits between a user's browser and the web application.
  • Admin consoles served to a browser. The flaw sits between a user's browser and the web application.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Between a user's browser and the web application. An attacker who crosses it can act inside a signed-in user's browser session.

Questions to answer about your own systems

  • Where does coder run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.