Is flask 3.1 vulnerable?

PyPI · 4 releases from 3.1.0 to 3.1.3 · latest flask is 3.1.3 · checked 18 Nov 2026

No known advisories in the last release

flask 3.1.3, the last 3.1 release, has no known advisories. 2 advisories affect earlier 3.1.x releases, so update to 3.1.3.

Update within 3.1:pip install 'flask>=3.1.3'

Is your project on an affected flask?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.1.x, affecting earlier releases

  • LowCVE-2026-27205GHSA-68rp-wp8r-472619 Feb 2026

    Flask session does not add `Vary: Cookie` header when accessed in some ways

    Affected
    <3.1.3
    Fixed in
    3.1.3
  • LowCVE-2025-47278GHSA-4grg-w6v8-c28g13 May 2025

    Flask uses fallback key instead of current signing key

    Affected
    >=3.1.0 <3.1.1
    Fixed in
    3.1.1

Every flask 3.1.x release

Affected: 3.1.0 to 3.1.2. 3.1.3 is not affected.

VersionKnown advisories
flask 3.1.3None
flask 3.1.2CVE-2026-27205
flask 3.1.1CVE-2026-27205
flask 3.1.0CVE-2026-27205, CVE-2025-47278

Which of your client projects are still on flask 3.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact flask version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other flask versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.