CVE-2026-46715
Medium
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.
SeverityMedium
CVSS5.3
Exploit probability—
ProductFlask-security-too
PublishedJul 20, 2026
First seenJul 20, 2026
Weakness typeCWE-287Improper authentication
How to fix
Update
- flask-security-too5.8.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| flask-security-tooPyPI | 5.8.0 ≤ v < 5.8.1 | 5.8.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.