CVE-2026-46715

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2026-46715
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46715.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-46715
Aliases
Published
2026-07-20T17:10:27.014Z
Modified
2026-07-25T03:56:42.033777628Z
Severity
  • 5.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N CVSS Calculator
Summary
Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
Details

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.

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46715.json",
    "cwe_ids": [
        "CWE-287"
    ],
    "cna_assigner": "GitHub_M"
}
References

Affected packages

Git / github.com/pallets-eco/flask-security

Affected ranges

Type
GIT
Repo
https://github.com/pallets-eco/flask-security
Events
Introduced
08288dff6907e413d848a16aaf43fc2c2b2a3b72
Fixed
8e69f3a94a463c0e8ddc46e31743717559fd8d48
Database specific 
{
    "source": [
        "AFFECTED_FIELD",
        "REFERENCES"
    ],
    "extracted_events": [
        {
            "introduced": "5.8.0"
        },
        {
            "fixed": "5.8.1"
        }
    ]
}

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46715.json"