CVE-2026-46715 Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
MediumCVSS 5.3
EPSS 0.35%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| pypi flask-security-too(PyPI) | = 5.8.0; >= 5.8.0, < 5.8.1 | 5.8.1 | Fixed |
| pallets-eco Flask-Security-Too | = >= 5.8.0, < 5.8.1 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| pypi flask-security-too(PyPI) | >= 5.8.0, < 5.8.1 | 5.8.1 |
| pypi flask-security-too(PyPI) | = 5.8.0 | No fix listed |
| pallets-eco Flask-Security-Too | = >= 5.8.0, < 5.8.1 | No fix listed |
References
- https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x-p63p exploit vendor-advisory
- github.com product
- pypi.org product
- github.com vendor-advisory
- nvd.nist.gov vendor-advisory
- https://github.com/pallets-eco/flask-security/commit/8e69f3a94a463c0e8ddc46e31743717559fd8d48