Skip to main content
Vulnerability Database/CVE-2025-71435

CVE-2025-71435: Coder Session Expiration Bypass Vulnerability

CVE-2025-71435 is an authentication bypass flaw in Coder that lets users maintain access after OIDC token expiration. This post covers the technical details, affected versions, security impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-71435 Overview

Coder versions before 2.23.0 contain a session expiration bypass vulnerability tracked as CVE-2025-71435. The flaw allows authenticated users to retain access after their OpenID Connect (OIDC) token expires when the identity provider does not issue a refresh token. Instead of being forced to re-authenticate, users can keep their APIKey cookie active through regular interaction with Coder. Each use extends the session by 24 hours, enabling indefinite access after OIDC authorization has been revoked. The weakness is classified as [CWE-613: Insufficient Session Expiration].

Critical Impact

Authenticated users who have lost OIDC authorization can continue accessing Coder indefinitely by extending their API key cookie through normal usage.

Affected Products

  • Coder versions prior to 2.23.0
  • Deployments configured with OIDC identity providers that do not issue refresh tokens
  • Self-hosted Coder installations relying on OIDC for session lifecycle enforcement

Discovery Timeline

  • 2026-10-17 - CVE-2025-71435 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in the NVD database

Technical Details for CVE-2025-71435

Vulnerability Analysis

Coder issues an APIKey cookie to authenticated users after a successful OIDC login. The server is expected to validate ongoing session legitimacy by refreshing the underlying OIDC token when it expires. When the identity provider does not return a refresh token during the initial authorization code exchange, Coder cannot renew the OIDC session. However, the application continues to treat the APIKey cookie as the authoritative session artifact and extends its lifetime by 24 hours on every request.

This decouples the application session from the identity provider session. A user removed from the identity provider, disabled, or whose group memberships change retains full access to Coder as long as they keep interacting with the platform. The vulnerability maps to [CWE-613] because session expiration is not enforced against the upstream authority after OIDC token expiry.

Root Cause

The root cause is a session lifecycle gap in how Coder reconciles the APIKey cookie with OIDC token state. When no refresh token exists, the application silently falls back to extending the local cookie rather than invalidating the session or forcing re-authentication. There is no enforcement path that requires revalidation with the identity provider after the original OIDC access token expires.

Attack Vector

An authenticated user whose OIDC authorization has been revoked by an administrator can continue to send requests to Coder using their existing APIKey cookie. Each request resets the 24-hour sliding window, producing a de facto permanent session. Exploitation requires low privileges, a network path to the Coder instance, and no user interaction beyond continued normal use. See the GitHub Security Advisory GHSA-3rw9-wmc8-8948 and the VulnCheck advisory for additional technical context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-71435

Indicators of Compromise

  • Active Coder sessions belonging to users who have been disabled, removed, or deprovisioned in the OIDC identity provider.
  • APIKey cookies with repeatedly extended expiration timestamps on accounts that have not performed a fresh OIDC login in an extended period.
  • Audit log entries showing continued Coder API activity from accounts whose last successful OIDC authentication exceeds the identity provider's access token lifetime.

Detection Strategies

  • Correlate Coder authentication logs with identity provider logs to identify sessions active beyond the last successful OIDC authorization event.
  • Enumerate accounts in Coder and compare their active session state against the current enabled user set in the OIDC provider.
  • Review identity provider configuration to determine whether refresh tokens are being issued; sessions without refresh tokens are the exposed population.

Monitoring Recommendations

  • Centralize Coder audit logs and OIDC identity provider logs in a security data lake to enable cross-source session reconciliation.
  • Alert on API activity from users whose identity provider account has been disabled, deleted, or had group memberships altered.
  • Track APIKey cookie lifetime extensions beyond expected re-authentication intervals and flag accounts that never trigger a new OIDC login.

How to Mitigate CVE-2025-71435

Immediate Actions Required

  • Upgrade all Coder deployments to version 2.23.0 or later to apply the vendor fix.
  • Audit active Coder sessions and revoke APIKey cookies for users who have been removed or disabled in the OIDC identity provider.
  • Review OIDC client configuration and enable refresh tokens where the identity provider supports them to restore the intended session lifecycle.

Patch Information

Coder resolved CVE-2025-71435 in version 2.23.0. Administrators should follow the upgrade guidance in the GitHub Security Advisory GHSA-3rw9-wmc8-8948. After upgrading, confirm that session invalidation occurs when OIDC tokens expire without a refresh token, and validate behavior against the identity provider configuration in use.

Workarounds

  • Configure the OIDC identity provider to issue refresh tokens so that Coder can validate ongoing authorization at the identity layer.
  • Shorten the maximum session lifetime for Coder API keys to reduce the window during which a revoked user can maintain access.
  • Force periodic re-authentication for all Coder users by invalidating active sessions on a defined schedule until the upgrade is complete.
bash
# Configuration example
# Verify installed Coder version and upgrade to the patched release
coder --version
# Upgrade to 2.23.0 or later per the vendor release notes
# Example (binary install): download the 2.23.0+ release and replace the server binary, then restart the service
systemctl restart coder

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.