Advisory

GHSA-68rp-wp8r-4726

Also known as: CVE-2026-27205, PYSEC-2026-2151

Summary

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

Details

When the session object is accessed, Flask should set the Vary: Cookie header. This instructs caches not to cache the response, as it may contain information specific to a logged in user. This is handled in most cases, but some forms of access such as the Python in operator were overlooked.

The severity depends on the application's use of the session, and the cache's behavior regarding cookies. The risk depends on all these conditions being met.

  1. The application must be hosted behind a caching proxy that does not ignore responses with cookies.
  2. The application does not set a Cache-Control header to indicate that a page is private or should not be cached.
  3. The application accesses the session in a way that does not access the values, only the keys, and does not mutate the session.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-02-19 20:45 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

flask

PyPI · All systems

Affected

  • introduced 0, fixed 3.1.3 (ecosystem)

Fixed versions

3.1.3

Fix

  • Fixed version 3.1.3
    pip install --upgrade flask==3.1.3

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences