Coder up to 2.38.1 Web Dashboard SESSION_TOKEN access control

Summaryinfo

A vulnerability, which was classified as critical, has been found in Coder up to 2.29.22/2.34.13/2.36.8/2.37.5/2.38.1. The impacted element is an unknown function of the component Web Dashboard. Performing a manipulation of the argument SESSION_TOKEN results in access control. This vulnerability was named CVE-2026-126308. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Coder up to 2.29.22/2.34.13/2.36.8/2.37.5/2.38.1. This affects an unknown functionality of the component Web Dashboard. The manipulation of the argument SESSION_TOKEN with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The web dashboard in Coder 2.24.0 before 2.29.23, 2.30.0 before 2.34.14, 2.35.0 before 2.36.9, 2.37.0 before 2.37.6, and 2.38.0 before 2.38.2 replaces the $SESSION_TOKEN placeholder in external app URLs with a full-access API key without checking whether the app belongs to a sub-agent. Code running in a workspace can register a disguised sub-agent app with a custom protocol URL, so the owner's click sends their API key to an attacker-chosen destination.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-126308 since 11/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 2.29.23, 2.34.14, 2.36.9, 2.37.6 or 2.38.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Coder

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.29.17
• 2.29.18
• 2.29.19
• 2.29.20
• 2.29.21
• 2.29.22
• 2.34.0
• 2.34.1
• 2.34.2
• 2.34.3
• 2.34.4
• 2.34.5
• 2.34.6
• 2.34.7
• 2.34.8
• 2.34.9
• 2.34.10
• 2.34.11
• 2.34.12
• 2.34.13
• 2.36.0
• 2.36.1
• 2.36.2
• 2.36.3
• 2.36.4
• 2.36.5
• 2.36.6
• 2.36.7
• 2.36.8
• 2.37.0
• 2.37.1
• 2.37.2
• 2.37.3
• 2.37.4
• 2.37.5
• 2.38.0
• 2.38.1

Website

• Product: https://github.com/coder/coder/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion