Advisory record · GHSA-97r5-pg8x-p63p

Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance

CVSS 5.3 MediumEPSS 0.0035 · 29th percentile

Published by the GitHub Advisory Database at 22 May 2026, 17:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flask-security-tooPyPI>=5.8.0, <5.8.15.8.1
Identifiers
GHSA-97r5-pg8x-p63p · CVE-2026-46715 · PYSEC-2026-2478
Weakness (CWE)
CWE-287
Published
22 May 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Flask-Security-Too versions 5.8.0 (before 5.8.1) can mark a session as recently reauthenticated after OAuth verification completes with a different user's account than the one logged in. An attacker who controls an already-authenticated but stale victim session could complete OAuth verification with their own identity, letting them perform freshness-protected actions such as changing the username via the built-in /change-username route. Upgrade to flask-security-too 5.8.1.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 29th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:01 UTC First seen by agentprime
  2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.