Coder up to 2.29.16/2.32.6/2.33.7/2.34.1 Password Management /api/v2/users improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.57+ |
Summary
A vulnerability was found in Coder up to 2.29.16/2.32.6/2.33.7/2.34.1. It has been classified as problematic. This vulnerability affects unknown code of the file /api/v2/users of the component Password Management. Performing a manipulation results in improper authorization. This vulnerability is identified as CVE-2026-55077. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in Coder up to 2.29.16/2.32.6/2.33.7/2.34.1. This affects an unknown code block of the file /api/v2/users of the component Password Management. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the `PUT /api/v2/users/{user}/password` endpoint authorized only `ActionUpdatePersonal` and did not prevent a `user-admin` from resetting an `owner` account's password. It also did not require the current password when an admin reset another user's password. Exploitation requires the privileged `user-admin` role so practical risk is limited to deployments that grant `user-admin` to less trusted operators. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 prevents non-owner users from resetting the password of an account that holds the `owner` role. As a workaround, restrict the `user-admin` role to trusted administrators.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-55077 since 06/16/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.
Upgrading to version 2.29.17, 2.32.7, 2.33.8 or 2.34.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-42130). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
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.32.0
- 2.32.1
- 2.32.2
- 2.32.3
- 2.32.4
- 2.32.5
- 2.32.6
- 2.33.0
- 2.33.1
- 2.33.2
- 2.33.3
- 2.33.4
- 2.33.5
- 2.33.6
- 2.33.7
- 2.34.0
- 2.34.1
Website
- Product: https://github.com/coder/coder/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: Coder 2.29.17/2.32.7/2.33.8/2.34.2
Timeline
06/16/2026 CVE reserved07/07/2026 VulDB entry created
07/08/2026 Advisory disclosed
07/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-55077 (🔒)
GCVE (CVE): GCVE-0-2026-55077
GCVE (VulDB): GCVE-100-376731
EUVD: 🔒
Entry
Created: 07/08/2026 01:10Updated: 07/08/2026 03:56
Changes: 07/08/2026 01:10 (53), 07/08/2026 03:56 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.