vulns.co
/
GKData.io MCP and API Buy me a coffee

Bugsink

Bugsink: time-unit consistency in account-access token expiry

Bugsink interpreted token lifetimes expressed in seconds as days. Its maintainer reports that unused email-verification, password-reset and new-user setup links therefore stayed valid beyond their intended expiry.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

Editorial lesson: represent security durations with explicit units and verify expiration independently of single-use behavior. The maintainer lists versions before 2.5.1 as affected and identifies 2.5.1 as correcting the unit conversion and removing over-age tokens before acceptance.

Before reading

  • Basic server-side identity and authorization concepts

Context and limits

  • Requires possession of an unused token; the advisory says random tokens are not practically guessable. Access remains within the associated account’s permissions, without adding team or project memberships. Successful use deletes the token.
  • The source describes possible unauthorized login after expiry, not a documented production compromise or observed theft. The fix is maintainer-reported; this review did not independently assess deployments or session cleanup.
  • vanschelven published the advisory; no separate reporter is named. The original report date is unknown. Learning prerequisites are editorial.

Sources

  1. Email verification, password-reset, and new-user setup links remain valid beyond their configured lifetimeBugsink · reviewed 2026-10-03
  2. Bugsink changelog: 2.5.1Bugsink · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software