CVE-2026-46715: CWE-287: Improper Authentication in pallets-eco Flask-Security-Too
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.
AI Analysis
Technical Summary
CVE-2026-46715 is an improper authentication vulnerability (CWE-287) in Flask-Security-Too version 5.8.0. The OAuth reauthentication flow incorrectly marks a session as fresh after verifying an OAuth account that does not belong to the original user of the session. An attacker who can operate a victim's stale authenticated session can complete OAuth verification using their own OAuth identity, causing the victim's session to be treated as recently reauthenticated. This bypasses freshness protections on sensitive account actions. The issue is fixed in version 5.8.1.
Potential Impact
An attacker able to use a stale but authenticated victim session can escalate privileges by causing the session to be treated as freshly authenticated. This allows the attacker to perform account actions that require recent reauthentication, potentially leading to unauthorized sensitive operations within the affected Flask application.
Mitigation Recommendations
Upgrade Flask-Security-Too to version 5.8.1 or later, which contains a fix for this improper authentication vulnerability. No other mitigations are specified. Patch status is confirmed by the vendor's versioning.
CVE-2026-46715: CWE-287: Improper Authentication in pallets-eco Flask-Security-Too
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.
CVSS v4.0
Score 5.3medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-46715 is an improper authentication vulnerability (CWE-287) in Flask-Security-Too version 5.8.0. The OAuth reauthentication flow incorrectly marks a session as fresh after verifying an OAuth account that does not belong to the original user of the session. An attacker who can operate a victim's stale authenticated session can complete OAuth verification using their own OAuth identity, causing the victim's session to be treated as recently reauthenticated. This bypasses freshness protections on sensitive account actions. The issue is fixed in version 5.8.1.
Potential Impact
An attacker able to use a stale but authenticated victim session can escalate privileges by causing the session to be treated as freshly authenticated. This allows the attacker to perform account actions that require recent reauthentication, potentially leading to unauthorized sensitive operations within the affected Flask application.
Mitigation Recommendations
Upgrade Flask-Security-Too to version 5.8.1 or later, which contains a fix for this improper authentication vulnerability. No other mitigations are specified. Patch status is confirmed by the vendor's versioning.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-15T23:26:58.309Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5e61922a4a8d59897a5062
Added to database: 07/20/2026, 17:57:38 UTC
Last enriched: 07/20/2026, 18:12:28 UTC
Last updated: 07/21/2026, 03:50:28 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.