CVE-2025-58437
Coder 2.22 – 2.24.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2025-58437 is a high-severity Insecure Inherited Permissions (CWE-277) vulnerability in Coder Coder. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-12 (Session Termination) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-27069
Vulnerability Data
Coder allows organizations to provision remote development environments via Terraform. In versions 2.22.0 through 2.24.3, 2.25.0 and 2.25.1, Coder can be compromised through insecure session handling in prebuilt workspaces. Coder automatically generates a session token for a user when a…
more
workspace is started. It is automatically exposed via coder_workspace_owner.session_token. Prebuilt workspaces are initially owned by a built-in prebuilds system user. When a prebuilt workspace is claimed, a new session token is generated for the user that claimed the workspace, but the previous session token for the prebuilds user was not expired. Any Coder workspace templates that persist this automatically generated session token are potentially impacted. This is fixed in versions 2.24.4 and 2.25.2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 10 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
AC-12 directly requires automatic session termination after a defined period, structurally preventing reuse of expired session identifiers.
Enforcing approved authorizations structurally stops the runtime assignment of permissions that violate user intent.
Least privilege requires that only the minimal necessary permissions are granted, which structurally prevents the definition and inheritance of overly broad permissions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Credential lifecycle management directly includes enforcing session expiration to prevent reuse.
Directly addresses defining and enforcing secure access permissions and least privilege, which prevents insecure inheritance.
Authentication mechanisms can incorporate session timeout checks but do not inherently address expiration policy.
Configuration management practices include establishing secure permission baselines that avoid insecure inheritance.
Secure SDLC practices would catch and prevent defining insecure inherited permissions during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing may detect permission issues but does not prevent insecure inheritance by design.
Restricting privileged utility programs reduces the chance that such tools will incorrectly alter object permissions.
Privileged access rights management can limit inheritance of excessive permissions but does not directly address insecure default permission inheritance.
Secure development lifecycle practices can include permission model reviews but do not guarantee secure inherited permissions.
Secure system architecture principles can incorporate least-privilege permission models but do not specifically mandate secure inheritance.
Secure coding standards can explicitly require setting restrictive permissions at object creation, directly mitigating insecure inheritance.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (2 rules)
- V-224974 Domain-created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277
- V-224972 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-277
Windows Server 2019 (2 rules)
- V-205743 Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277
- V-205741 Windows Server 2019 Active Directory Group Policy objects must have proper access control permissions. prevents CWE-277
Windows Server 2022 (1 rule)
- V-254395 Windows Server 2022 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-277