CVE-2026-126404: Coder from 2.38.0 before 2.38.4 Privilege Escalation via API Key Creation
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: coder coder 2.29.24, 2.34.16, 2.36.0.
Low priority for now. Upgrade to coder coder 2.29.24, 2.34.16, 2.36.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Coder 2.28.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 does not restrict new API keys to the creating token's scopes, allow list, or expiry. A scoped API key or OAuth2 token holding key-creation permission can call POST /api/v2/users/{user}/keys/tokens to mint longer-lived coder:all keys, gaining the user's full privileges.
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- EPSS
- —
- CWE
- CWE-266
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 7.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
coder coder
- 2.38.4, 2.37.8, 2.36.11, 2.34.16, 2.29.24, 2.36.0not affected
- 2.38.0 and later · before 2.38.4affected · semver
- 2.37.0 and later · before 2.37.8affected · semver
- 2.36.0 and later · before 2.36.11affected · semver
- 2.30.0 and later · before 2.34.16affected · semver
- 2.28.0 and later · before 2.29.24affected · semver
- 2.35.0 and later · before 2.36.0affected · semver
Same product
coder: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-46354Coder: PKCS#7 signature bypass in Azure instance identity allows unauthenticated agent token theft36Monitor
- CVE-2026-44454Coder vulnerable to workspace auto-creation via crafted URL parameters without user consent36Monitor
- CVE-2026-126403Coder 2.38.0 before 2.38.4 Authorization Bypass via External Agent Credentials Endpoint34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-121967Nov 4, 2026 · Coder before 2.29.22, 2.34.13, 2.35.10, 2.36.8, 2.37.5, and 2.38.1 AI Gateway Path Traversal9Monitor
- ← EarlierCVE-2026-126308Nov 13, 2026 · Coder 2.38.0 before 2.38.2 Session Token Leak via Sub-Agent External Apps34Monitor
- Later →CVE-2026-126405Nov 13, 2026 · Coder from 2.38.0 before 2.38.4 Memory Exhaustion DoS via Web Push28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| coder coder | 2.29.24 | Vendor (CNA) |
| coder coder | 2.34.16 | Vendor (CNA) |
| coder coder | 2.36.0 | Vendor (CNA) |
| coder coder | 2.36.11 | Vendor (CNA) |
| coder coder | 2.37.8 | Vendor (CNA) |
| coder coder | 2.38.4 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026same day
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- MutedCybersecurityreporter
- EhabYremediation developer
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-266 · Incorrect Privilege AssignmentCVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.