CVE-2026-46715 Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
Attackers can bypass reauthentication checks by linking their OAuth identity to a victim's stale session, enabling unauthorized account actions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-46715?
CVE-2026-46715 is a medium-severity authentication bypass vulnerability in pallets-eco Flask-Security-Too, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-287
Which versions are affected by CVE-2026-46715?
3 open source packages ship an affected version, including flask-security-too and Flask-Security-Too.
| Package | Affected | Fixed in |
|---|---|---|
flask-security-too PyPI | From 5.8.0 | 5.8.1 |
flask-security-too PyPI | From 5.8.0 | 5.8.1 |
Flask-Security-Too PyPI | From 5.8.0 | 5.8.1 |
How do I fix CVE-2026-46715?
Upgrade flask-security-too to 5.8.1 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-46715 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46715 exists.
Sources
Also known as GHSA-97r5-pg8x-p63p, PYSEC-2026-2478.