<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 21:49:05 +0000</lastBuildDate>
    <item>
      <title>GHSA-68rp-wp8r-4726 — Flask session does not add `Vary: Cookie` header when accessed in some ways</title>
      <link>https://db.gcve.eu/vuln/ghsa-68rp-wp8r-4726</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: flask&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The severity depends on the application&amp;#39;s use of the session, and the cache&amp;#39;s behavior regarding cookies. The risk depends on all these conditions being met.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: flask&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The severity depends on the application&amp;#39;s use of the session, and the cache&amp;#39;s behavior regarding cookies. The risk depends on all these conditions being met.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-68rp-wp8r-4726</guid>
    </item>
  </channel>
</rss>
