cve.bz

CVE-2026-126308 Coder 2.38.0 before 2.38.2 Session Token Leak via Sub-Agent External Apps

8.7 highEPSS 0.3%

High (8.7) in coder coder. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-201 Insertion of Sensitive Information Into Sent Data
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126308 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126308?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126308?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126308 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126308

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126308](https://cve.bz/cve/badge/CVE-2026-126308.svg)](https://cve.bz/cve/CVE-2026-126308)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126308"><img src="https://cve.bz/cve/badge/CVE-2026-126308.svg" alt="CVE-2026-126308"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
coderfrom 2.38.0 before 2.38.2
coderfrom 2.37.0 before 2.37.6
coderfrom 2.36.0 before 2.36.9
coderfrom 2.30.0 before 2.34.14
coderfrom 2.24.0 before 2.29.23
coderfrom 2.35.0 before 2.36.0

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON