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