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

Advisory record · `GHSA-97r5-pg8x-p63p`

- **Identifiers:** `GHSA-97r5-pg8x-p63p` · `CVE-2026-46715` · `PYSEC-2026-2478`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 22 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `flask-security-too` (PyPI): affected `>=5.8.0, <5.8.1`; fixed in `5.8.1`

## 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

- 5.3 Medium, CVSS 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`, from 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

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-97r5-pg8x-p63p)

## Sources

- [GitHub Advisory Database: GHSA-97r5-pg8x-p63p](https://github.com/advisories/GHSA-97r5-pg8x-p63p)
- [OSV: GHSA-97r5-pg8x-p63p](https://osv.dev/vulnerability/GHSA-97r5-pg8x-p63p)
- <https://github.com/pallets-eco/flask-security/security/advisories/GHSA-97r5-pg8x-p63p>
- <https://github.com/pallets-eco/flask-security>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-97r5-pg8x-p63p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-97r5-pg8x-p63p/>. Everything for agents: <https://agentprime.io/llms.txt>.
