GPU VulnDB

Database/Control plane, storage & DevOps

Coder: prebuilds system-user session token survives workspace claim and stays valid

CVSS 8.1CVE-2025-58437Control plane, storage & DevOpscurated

Impact

Coder issues a session token into each workspace at start time and exposes it as coder_workspace_owner.session_token. Prebuilt workspaces start as the built-in prebuilds system user; when a real user claims one, a new token is minted but the prebuilds user's old token is never expired. Any template that persists that token leaves a live credential for a privileged built-in account inside a workspace now owned by someone else - whoever can read the workspace filesystem or environment can act as the prebuilds user against the Coder API. On a fleet where Coder hands out GPU dev workspaces to many users, that is a lateral path from one tenant's workspace into workspace provisioning.

Who can reach it

Network, authenticated as a low-privileged Coder user (PR:L) who claims or can read a prebuilt workspace. Only deployments using prebuilt workspaces with templates that persist the session token are affected.

What to do

Upgrade Coder to 2.24.4 or 2.25.2 and restart coderd. Then rotate: revoke the prebuilds user's outstanding tokens and recycle existing prebuilt workspaces, since the upgrade does not invalidate tokens already written into running workspaces. Review templates for anything that writes coder_workspace_owner.session_token to disk and stop persisting it.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.