What’s Vulnerable › Vulnerabilities
CVE-2026-46715: Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
- Severity: medium (CVSS 5.3 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-07-20 · updated 2026-10-24
- Weakness: CWE-287
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.
Affected products
- pallets-eco Flask-Security-Too: from 5.8.0, < 5.8.1
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
Get alerted when CVE-2026-46715 or the next vulnerability affects your stack