CVE-2026-43983: fallo de gravedad alta en pocket-id
Pocket ID: OIDC refresh token flow bypasses authorization revocation, account disabling, and group restrictions
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.5epss 0.2%
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Productos afectados
pocket-id · pocket-idCVEs relacionadas — pocket-id
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-55834MEDIUMPocket ID: Open Redirect on the OIDC /authorize page via unvalidated redirect_uri with prompt=noneEPSS 0.4%CVE-2026-28513HIGHPocket ID: OIDC authorization code validation uses AND instead of OR, allowing cross-client token exchangeEPSS 0.3%CVE-2026-62662HIGHPocket ID: Client credentials grant allows any OIDC client to obtain tokens for arbitrary audiencesEPSS 0.3%CVE-2026-28512HIGHPocket ID: OAuth redirect_uri validation bypass via userinfo/host confusionEPSS 0.2%CVE-2026-115770CRITICALPocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofingEPSS 0.2%