CVE Catalog

CVE-2026-46715

MediumCVSS 5.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.28%

20th percentile - higher than 20% of all known CVEs

Summary

Vulnerability in Flask-Security-Too version 5.8.0 in the OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account belonging to a different user. An attacker can use an authenticated but stale victim session to perform freshness-protected actions.

Risk Assessment

The risk involves session hijacking and performing sensitive operations on the victim's account, such as password or data changes.

Recommendation

It is recommended to update Flask-Security-Too to version 5.8.1, which contains the fix.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS