Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Pocket ID versions before 0.0.0-20260307173642-b59e35cb59ae accept OIDC authorization codes at the token endpoint when the client ID is wrong or the code has expired, because a logic check uses AND instead of OR. An attacker who controls a registered OIDC client can exchange a code issued to a different client for tokens for users who never authorized their client, and can reuse expired codes with the correct client until cleanup runs. Upgrade to 0.0.0-20260307173642-b59e35cb59ae or later.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0031, the 24th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:09 UTC First seen by agentprime
- 31 Oct 2026, 15:09 UTC Confirmed by OSV