<?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://vulnerability.circl.lu</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>Wed, 30 Sep 2026 01:28:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-30861 — Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-30861</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pallets flask&lt;/p&gt;
&lt;p&gt;Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets `session.permanent = True`
3. The application does not access or modify the session at any point during a request.
4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pallets flask&lt;/p&gt;
&lt;p&gt;Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets `session.permanent = True`
3. The application does not access or modify the session at any point during a request.
4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-30861</guid>
    </item>
    <item>
      <title>GHSA-m2qf-hxjv-5gpq — Flask vulnerable to possible disclosure of permanent session cookie due to missing Vary: Cookie header</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-m2qf-hxjv-5gpq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: Flask&lt;/p&gt;
&lt;p&gt;When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by a proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session, and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets [`session.permanent = True`](https://flask.palletsprojects.com/en/2.3.x/api/#flask.session.permanent).
2. The application does not access or modify the session at any point during a request.
4. [`SESSION_REFRESH_EACH_REQUEST`](https://flask.palletsprojects.com/en/2.3.x/config/#SESSION_REFRESH_EACH_REQUEST) is enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified.&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 all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by a proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session, and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets [`session.permanent = True`](https://flask.palletsprojects.com/en/2.3.x/api/#flask.session.permanent).
2. The application does not access or modify the session at any point during a request.
4. [`SESSION_REFRESH_EACH_REQUEST`](https://flask.palletsprojects.com/en/2.3.x/config/#SESSION_REFRESH_EACH_REQUEST) is enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-m2qf-hxjv-5gpq</guid>
    </item>
    <item>
      <title>PYSEC-2023-62</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2023-62</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: flask&lt;/p&gt;
&lt;p&gt;Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets `session.permanent = True`
3. The application does not access or modify the session at any point during a request.
4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: flask&lt;/p&gt;
&lt;p&gt;Flask is a lightweight WSGI web application framework. When all of the following conditions are met, a response containing data intended for one client may be cached and subsequently sent by the proxy to other clients. If the proxy also caches `Set-Cookie` headers, it may send one client&amp;#39;s `session` cookie to other clients. The severity depends on the application&amp;#39;s use of the session and the proxy&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 strip cookies or ignore responses with cookies.
2. The application sets `session.permanent = True`
3. The application does not access or modify the session at any point during a request.
4. `SESSION_REFRESH_EACH_REQUEST` enabled (the default).
5. The application does not set a `Cache-Control` header to indicate that a page is private or should not be cached.&lt;/p&gt;
&lt;p&gt;This happens because vulnerable versions of Flask only set the `Vary: Cookie` header when the session is accessed or modified, not when it is refreshed (re-sent to update the expiration) without being accessed or modified. This issue has been fixed in versions 2.3.2 and 2.2.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2023-62</guid>
    </item>
  </channel>
</rss>
