What is CVE-2026-55077?

CVE-2026-55077 is a high-severity security vulnerability in github.com/coder/coder/v2 (go), affecting versions >= 2.34.0, < 2.34.2. It is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17.

How severe is CVE-2026-55077?

CVE-2026-55077 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/coder/coder/v2 are affected by CVE-2026-55077?

github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.

Is there a fix for CVE-2026-55077?

Yes. CVE-2026-55077 is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.

Is CVE-2026-55077 exploitable, and should I be worried?

Whether CVE-2026-55077 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-55077 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-55077?

Upgrade: github.com/coder/coder/v2 to 2.34.2 or later, github.com/coder/coder/v2 to 2.33.8 or later, github.com/coder/coder/v2 to 2.32.7 or later, github.com/coder/coder/v2 to 2.29.17 or later.

CVE-2026-55077 in github.com/coder/coder/v2

Q: How severe is CVE-2026-55077?

CVE-2026-55077 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/coder/coder/v2 are affected by CVE-2026-55077?

github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.

Q: Is there a fix for CVE-2026-55077?

Yes. CVE-2026-55077 is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.

Q: Is CVE-2026-55077 exploitable, and should I be worried?

Whether CVE-2026-55077 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-55077 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-55077?

Upgrade: github.com/coder/coder/v2 to 2.34.2 or later, github.com/coder/coder/v2 to 2.33.8 or later, github.com/coder/coder/v2 to 2.32.7 or later, github.com/coder/coder/v2 to 2.29.17 or later.

Summary

Coder: User-admin role can reset owner account password

Full technical description

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.

Note: Exploitation requires the privileged user-admin role so practical risk is limited to deployments that grant user-admin to less trusted operators.

Workarounds

Restrict the user-admin role to trusted administrators until upgrading.

Resources

Fix: #25709

Credits

Coder would like to thank Anthropic's Security Team (ANT-2026-22436) for independently disclosing this issue!

Impact

A user-admin could reset any owner's password without knowing it, authenticate as that owner and gain full deployment control, including templates, workspaces, licensing, organization settings and the ability to self-assign the owner role. This was a privilege escalation from user-admin to owner.

CVE-2026-55077 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.34.2, 2.33.8, 2.32.7, 2.29.17); upgrading removes the vulnerable code path.

Affected versions

github.com/coder/coder/v2 (>= 2.34.0, < 2.34.2) github.com/coder/coder/v2 (>= 2.33.0, < 2.33.8) github.com/coder/coder/v2 (>= 2.30.0, < 2.32.7) github.com/coder/coder/v2 (< 2.29.17)

Security releases

github.com/coder/coder/v2 → 2.34.2 (go) github.com/coder/coder/v2 → 2.33.8 (go) github.com/coder/coder/v2 → 2.32.7 (go) github.com/coder/coder/v2 → 2.29.17 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The fix prevents non-owner users from resetting the password of an account that holds the owner role.

The fix was backported to all supported release lines:

Release line	Patched version
2.34	v2.34.2
2.33	v2.33.8
2.32	v2.32.7
2.29 (ESR)	v2.29.17

Frequently Asked Questions

What is CVE-2026-55077? CVE-2026-55077 is a high-severity security vulnerability in github.com/coder/coder/v2 (go), affecting versions >= 2.34.0, < 2.34.2. It is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17.
How severe is CVE-2026-55077? CVE-2026-55077 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/coder/coder/v2 are affected by CVE-2026-55077? github.com/coder/coder/v2 (go) versions >= 2.34.0, < 2.34.2 is affected.
Is there a fix for CVE-2026-55077? Yes. CVE-2026-55077 is fixed in 2.34.2, 2.33.8, 2.32.7, 2.29.17. Upgrade to this version or later.
Is CVE-2026-55077 exploitable, and should I be worried? Whether CVE-2026-55077 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-55077 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-55077?
- Upgrade github.com/coder/coder/v2 to 2.34.2 or later
- Upgrade github.com/coder/coder/v2 to 2.33.8 or later
- Upgrade github.com/coder/coder/v2 to 2.32.7 or later
- Upgrade github.com/coder/coder/v2 to 2.29.17 or later

Other vulnerabilities in github.com/coder/coder/v2

CVE-IDSeverityPackage summary

GHSA-QRWJ-VH9X-GW5VHighgithub.com/coder/coder/v2: Coder's workspace agent API insecure redirect handling allowed cross-agent file read and write CVE-2026-55438Mediumgithub.com/coder/coder/v2: Coder's workspace app CORS origin check can be bypassed via UUID-based subdomain spoofing CVE-2026-55437Mediumgithub.com/coder/coder/v2: Coder vulnerable to stored HTML injection via workspace agent logs in AgentLogLine component CVE-2026-55436Highgithub.com/coder/coder/v2: Coder's AI Bridge Proxy skips TLS certificate verification in default configuration CVE-2026-55435Mediumgithub.com/coder/coder/v2: Suspended Coder users retain access to AI Bridge LLM proxy endpoints