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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary A session invalidation vulnerability exists in daptin's authentication system where JSON Web Tokens (JWTs) remain fully valid after a user changes their password. The JWT validation middleware (CheckJWT) only verifies token signature, expiry, issuer, and signing algorithm — it does not check whether the token was issued before the most recent password change. The password update code path hashes the new password but never calls InvalidateAuthCacheForEmail() and never revokes or blacklists existing tokens. This effectively negating password rotation as an incident response control. Vulnerable Files daptin/server/jwt/jwtmiddleware.go — JWT validation without session versioning daptin/server/resource/resourceupdate.go — password update without session invalidation daptin/server/actions/actiongeneratejwttoken.go — JWT claims lack password version daptin/server/auth/auth.go — InvalidateAuthCacheForEmail exists but not called on update daptin/server/resource/columns.go — password…

Published by the source

7 May 2026, 02:57 UTC

Last modified by the source

7 May 2026, 02:57 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-258c-965c-p3hc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-258c-965c-p3hc

Advisory: Daptin's Session Management Vulnerability Leads to Insufficient Session Expiration After Password Change
IDs: GHSA-258c-965c-p3hc
Record: https://patchnext.com/advisories/ghsa-258c-965c-p3hc (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/daptin/daptin 0.11.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/daptin/daptin: affected < 0.11.8; fixed in 0.11.8

## Suggested inspection (read-only)
- Go github.com/daptin/daptin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/daptin/daptin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-258c-965c-p3hc (GitHub-reviewed advisory GHSA-258c-965c-p3hc lists affected ranges: Go github.com/daptin/daptin >=0 <0.11.8)

Commands are suggestions: review each one before running it.