Advisories
This weekExploitable · Confirmed

flask-security-too: Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

flask-security-too (PyPI)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • flask-security-too (PyPI): from 5.8.0, before 5.8.1
  • flask-security-too (PyPI): from 5.8.0, before 5.8.1

The fix

  • flask-security-too (PyPI) fixed in 5.8.1

    pip
    python -m pip install flask-security-too==5.8.1
    uv
    uv add flask-security-too==5.8.1
    poetry
    poetry add flask-security-too@5.8.1
    Check what is installed
    python -m pip show flask-security-too
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency flask-security-too to 5.8.1 or the nearest later release, to fix CVE-2026-46715. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))