Advisory record · GHSA-258c-965c-p3hc

Daptin's Session Management Vulnerability Leads to Insufficient Session Expiration After Password Change

CVSS 6.5 Medium

Published by the GitHub Advisory Database at 7 May 2026, 02:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/daptin/daptinGo<0.11.80.11.8
Identifiers
GHSA-258c-965c-p3hc · GO-2026-4991
Weakness (CWE)
CWE-613
Published
7 May 2026
Updated
20 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Daptin versions before 0.11.8 do not invalidate existing JSON Web Tokens after a user changes their password, so a token issued before the change stays valid. An attacker who has obtained a token, for example one captured before a password reset, can keep reading and writing data through the API until the token expires. Upgrade to Daptin 0.11.8 or later. The source gives no other workaround.

Written 7 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
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

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