cve.bz

CVE-2026-126403 Coder 2.38.0 before 2.38.4 Authorization Bypass via External Agent Credentials Endpoint

8.5 highEPSS 0.4%

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

On this page
Coder 2.26.0 before 2.29.24, 2.30.0 before 2.34.16, 2.35.0 before 2.36.11, 2.37.0 before 2.37.8, and 2.38.0 before 2.38.4 contains an improper authorization flaw in the external agent credentials endpoint, which returns the workspace agent token to users with only workspace read access rather than ssh permission. Authenticated users with roles such as Template Admin or Organization Admin can use the token to read the owner's private Git SSH key and Git provider OAuth tokens, and impersonate the agent to receive the owner's sessions.

Severity

CVSS 4.0

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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126403 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126403?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126403?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-126403 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-126403

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-126403](https://cve.bz/cve/badge/CVE-2026-126403.svg)](https://cve.bz/cve/CVE-2026-126403)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
coderfrom 2.38.0 before 2.38.4
coderfrom 2.37.0 before 2.37.8
coderfrom 2.36.0 before 2.36.11
coderfrom 2.30.0 before 2.34.16
coderfrom 2.26.0 before 2.29.24
coderfrom 2.35.0 before 2.36.0

References

Check your stackJSON