# CVE-2025-71435: Coder session expiration bypass via OIDC without refresh token

Source: https://junglewise.ai/threats/cve-2025-71435-coder-before-2-23-0-contains-a-session-expiration-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-17. Updated: 2026-10-17  
License: CC BY 4.0 with a link back

CVE-2025-71435 · Severity: medium · CVSS 4.2 · Published 2026-10-17

Coder is a development environment management platform that enterprises use to provision remote development workspaces. A vulnerability allows authenticated users to maintain indefinite access to Coder even after their OIDC (OpenID Connect) authentication token expires, if the identity provider does not issue a refresh token. An attacker could exploit this to retain unauthorized access to development environments and systems after being revoked in the identity provider.

Technologies: [Coder](https://junglewise.ai/threats/technologies/coder). Vendors: [Coder](https://junglewise.ai/threats/vendors/coder).

## Quick answers

**Is CVE-2025-71435 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-71435 being exploited in the wild.

**How severe is CVE-2025-71435?** Medium severity, with a CVSS score of 4.2, published 17 October 2026.

**Which products and versions are affected?** Coder before 2.23.0.

**Is there a fix for CVE-2025-71435?** Yes: fixed in 2.23.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-71435 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-71435?** Check whether you run Coder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 2.23.0

## Technical details

When a user authenticates via OIDC without a refresh token, Coder fails to enforce the OIDC token expiry and allows continued API requests as long as the APIKey cookie remains valid. Coder's APIKey cookies have a 24-hour lifetime that automatically extends by up to 24 hours with each successful use, allowing indefinite session persistence. This affects versions before 2.23.0 and requires the attacker to be an already-authenticated user making requests at least once every 24 hours.

## Affected products

- Coder Coder before 2.23.0

## Timeline

- 2025-08-28: disclosed
- 2025-10-17: advisory

## References

- [https://github.com/coder/coder/security/advisories/GHSA-3rw9-wmc8-8948](https://github.com/coder/coder/security/advisories/GHSA-3rw9-wmc8-8948)
- [https://www.vulncheck.com/advisories/coder-before-2.23.0-session-expiration-bypass-via-oidc-without-refresh-token](https://www.vulncheck.com/advisories/coder-before-2.23.0-session-expiration-bypass-via-oidc-without-refresh-token)

## Related threats

- [Coder AI Gateway encoded path traversal](https://junglewise.ai/threats/cve-2026-121967-coder-2-28-0-before-2-29-22-2-30-0-before-2-34-13-2-35-0-before)
- [Coder missing audience validation in GCP instance-identity endpoint](https://junglewise.ai/threats/cve-2026-118687-coder-before-2-29-21-2-30-0-before-2-34-12-2-35-0-before-2-35-9)
- [Coder open redirect in workspace app proxy](https://junglewise.ai/threats/cve-2026-111931-coder-from-2-0-0-before-2-34-8-contains-an-open-redirect)
- [Coder workspace ACL endpoint authorization bypass](https://junglewise.ai/threats/cve-2026-111930-coder-from-2-26-0-before-2-34-8-contains-an-incorrect)
- [Coder provisioner daemon authorization bypass in DownloadFile](https://junglewise.ai/threats/cve-2026-111929-coder-from-2-30-0-before-2-34-8-contains-an-authorization-bypass)