Advisory record · GHSA-3rw9-wmc8-8948

Coder accepts an APIKey beyond the linked OIDC expiry if there is no refresh token

CVSS 2.3 LowEPSS 0.0018 · 7th percentile

Published by the GitHub Advisory Database at 28 Aug 2025, 19:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/coder/coder/v2Go<2.23.02.23.0
Identifiers
GHSA-3rw9-wmc8-8948 · CVE-2025-71435 · GO-2025-3921
Weakness (CWE)
CWE-324 · CWE-613
Published
28 Aug 2025
Updated
18 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Coder versions before 2.23.0 (github.com/coder/coder/v2) fail to enforce the expiry of an OIDC token when the identity provider returns no refresh token. A user whose OIDC login has expired can keep using the web session, and API requests succeed as long as their APIKey cookie is still valid, which can extend indefinitely if the key is used at least once every 24 hours. Upgrade to Coder 2.23.0 or later. The source gives no workaround.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.3 Low 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0018, the 7th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.