CVE-2026-28513 Pocket ID: OIDC authorization code validation uses AND instead of OR, allowing cross-client token exchange
Attackers can exchange authorization codes across clients or reuse expired codes due to flawed validation logic, potentially leading to unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-28513?
CVE-2026-28513 is a high-severity authentication bypass vulnerability in pocket-id, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to your services. Prior to 2.4.0, the OIDC token endpoint rejects an authorization code only when both the client ID is wrong and the code is expired. This allows cross-client code exchange and expired code reuse. This vulnerability is fixed in 2.4.0.
Weakness: CWE-863
Which versions are affected by CVE-2026-28513?
3 open source packages ship an affected version, including github.com/pocket-id/pocket-id/backend. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/pocket-id/pocket-id/backend Go | All versions | 0.0.0-20260307173642-b59e35cb59ae |
github.com/pocket-id/pocket-id/backend Go | All versions | 0.0.0-20260307173642-b59e35cb59ae |
github.com/pocket-id/pocket-id/backend Go | All versions | 0.0.0-20260307173642-b59e35cb59ae |
Products include Pocket-Id Pocket Id.
How do I fix CVE-2026-28513?
Upgrade github.com/pocket-id/pocket-id/backend to 0.0.0-20260307173642-b59e35cb59ae or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-28513 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28513 exists.
Other vulnerabilities in pocket-id
Sources
Also known as GHSA-qh6q-598w-w6m2, GO-2026-4656.