CVE-2026-46715

Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim session, they can complete OAuth verification using their own OAuth identity. The victim session is then treated as recently reauthenticated, allowing freshness-protected account actions to proceed. Version 5.8.1 contains a fix for this issue.

CVSS 4.0

5.3CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS

0.4% chance of exploitation in the next 30 days; higher than 28% of CVEs (scores of 2026-10-25)

CWE

CWE-287

Published

2026-07-20

Modified

2026-10-24

Record from

the NVD, synced 2026-10-25

Packages (OSV)

References

• https://github.com/pallets-eco/flask-security/commit/8e69f3a94a463c0e8ddc46e31743717559fd8d48
• https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x-p63p
• https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x-p63p

Check your stackJSON