ACCESS_TOKEN_EXPIRE_MINUTES is set to 60 * 60 (3600 minutes = 60 hours). Long-lived bearer tokens significantly increase impact of token theft and replay.
Severity: medium File: flowsint-core/src/flowsint_core/core/auth.py
Solution
Reduce access-token TTL (commonly 5–30 minutes), issue refresh tokens separately, and rotate/revoke tokens on sensitive events.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/reconurge/flowsint/pull/135
Author: @tuanaiseo
Created: 4/7/2026
Status: 🔄 Open
Base:
main← Head:contribai/fix/security/excessively-long-jwt-access-token-lifeti📝 Commits (1)
2dc267ffix(security): excessively long jwt access token lifetime📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
flowsint-core/src/flowsint_core/core/auth.py(+1 -1)📄 Description
Problem
ACCESS_TOKEN_EXPIRE_MINUTESis set to60 * 60(3600 minutes = 60 hours). Long-lived bearer tokens significantly increase impact of token theft and replay.Severity:
mediumFile:
flowsint-core/src/flowsint_core/core/auth.pySolution
Reduce access-token TTL (commonly 5–30 minutes), issue refresh tokens separately, and rotate/revoke tokens on sensitive events.
Changes
flowsint-core/src/flowsint_core/core/auth.py(modified)Testing
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.