Advisory record · GHSA-hp74-gm6m-2qm5

Pocket ID has a reauthentication bypass via one-time access token login — passkey step-up requirement defeated by JWT freshness check that accepts any login method

CVSS 4.0, no score published

Published by the GitHub Advisory Database at 28 Jul 2026, 14:25 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-20260419162744-978ac87deffe0.0.0-20260419162744-978ac87deffe
Identifiers
GHSA-hp74-gm6m-2qm5 · GO-2026-6117
Weakness (CWE)
CWE-287
Published
28 Jul 2026
Updated
18 Aug 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-20260419162744-978ac87deffe are affected. An attacker who holds a one-time access token or signup token can obtain a passkey reauthentication token without a passkey ceremony, because the reauthentication check only tests how recently the access token was issued. This lets them get OIDC access, ID and refresh tokens for clients configured to require reauthentication, and the refresh token can be renewed for 30 days. Upgrade to 0.0.0-20260419162744-978ac87deffe, which is the fixed version listed.

Written 6 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
Not published None 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

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