coder: Insertion of Sensitive Information Into Sent Data
CVE-2026-126308 is a high-severity insertion of sensitive information into sent data vulnerability in coder, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists versions 2.38.2, 2.37.6, 2.36.9 as the first without the flaw, so updating coder to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update coder to 2.38.2 or 2.37.6 or 2.36.9 or 2.34.14, whichever matches your release line, or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Coder | coder | 2.38.0 up to, but not including, 2.38.2; 2.37.0 up to, but not including, 2.37.6; 2.36.0 up to, but not including, 2.36.9; 2.30.0 up to, but not including, 2.34.14; 2.24.0 up to, but not including, 2.29.23; 2.35.0 up to, but not including, 2.36.0 | 2.38.2, 2.37.6, 2.36.9, 2.34.14, 2.29.23, 2.36.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.7 | High | CNA (vulncheck.com) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
How developers prevent this class of flaw
- Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
- Setup default error messages so that unexpected errors do not disclose sensitive information.
More Insertion of Sensitive Information Into Sent Data vulnerabilities (CWE-201)
Timeline
- CVE record published.
References
Other references
Other vulnerabilities in coder
- 7.7 High severity
- 8.3 High severity
- 7.4 High severity
- 8.7 High severity
- 8.2 High severity
- 8.3 High severity
Recent Insertion of Sensitive Information Into Sent Data vulnerabilities
- 10.0 Critical severity
- 7.5 High severity
- 9.1 Critical severity
- 8.3 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.