CVE-2026-43983

published 12 May 2026 · updated 11 Nov 2026

Pocket ID: OIDC refresh token flow bypasses authorization revocation, account disabling, and group restrictions

9.5CriticalCVSS 8.5EPSS 0%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.6.0.

Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to your services. Prior to 2.6.0, The createTokenFromRefreshToken function (oidc_service.go) validates the refresh token's cryptographic integrity but does not re-validate the user's current authorization state before issuing new tokens. This allows (1) the client to refresh the token indefinitely after authorization revocation, (2) the refresh token to continue to work after the account is disabled, and (3) the token to work after the client is removed from the group. This vulnerability is fixed in 2.6.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
pocket-idpocket_id<2.6.02.6.0
pocket-id<2.6.0

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43983 severity on Zeptric[![CVE-2026-43983](https://zeptric.io/badge/cve/CVE-2026-43983.svg)](https://zeptric.io/cve/CVE-2026-43983)