Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/pallets-eco/flask-security/commit/8e69f3a94a463c0e8ddc46e3174
- https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x
- https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x
FAQ
What is CVE-2026-46715?
CVE-2026-46715 is a documented vulnerability. 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 belo...
How severe is CVE-2026-46715?
CVSS scoring is not yet available for CVE-2026-46715. Check NVD for updates.
Is there a patch for CVE-2026-46715?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.