Advisory record · GHSA-qh6q-598w-w6m2

Pocket ID: OIDC authorization code validation uses AND instead of OR, allowing cross-client token exchange

CVSS 8.5 HighEPSS 0.0031 · 24th percentile

Published by the GitHub Advisory Database at 9 Mar 2026, 17:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/pocket-id/pocket-id/backendGo<0.0.0-20260307173642-b59e35cb59ae0.0.0-20260307173642-b59e35cb59ae
Identifiers
GHSA-qh6q-598w-w6m2 · CVE-2026-28513 · GO-2026-4656
Weakness (CWE)
CWE-863
Published
9 Mar 2026
Updated
23 Mar 2026

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.

Written 7 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
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

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 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.