Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-97r5-pg8x-p63p | Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance |
Thu, 23 Jul 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pallets-eco
Pallets-eco flask-security-too |
|
| Vendors & Products |
Pallets-eco
Pallets-eco flask-security-too |
Mon, 20 Jul 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 20 Jul 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-20T18:43:54.970Z
Reserved: 2026-05-15T23:26:58.309Z
Link: CVE-2026-46715
Updated: 2026-07-20T18:43:26.443Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-24T22:45:17Z
Github GHSA