https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:06:09 +0000 https://cve.radiocsirt.org/vuln/brew-aws-sam-cli-cve-2026-27205 <p><strong>Affected:</strong> Homebrew: aws-sam-cli</p> <p>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.</p> <p>The severity depends on the application&#39;s use of the session, and the cache&#39;s behavior regarding cookies. The risk depends on all these conditions being met.</p> <p>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.</p> <p><strong>Affected:</strong> Homebrew: aws-sam-cli</p> <p>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.</p> <p>The severity depends on the application&#39;s use of the session, and the cache&#39;s behavior regarding cookies. The risk depends on all these conditions being met.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/brew-aws-sam-cli-cve-2026-27205 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0395 certfr-2026-avi-0395 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0395 https://cve.radiocsirt.org/vuln/cleanstart-2026-an24336 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: airflow-2</p> <p>Multiple security vulnerabilities affect the airflow-2 package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: airflow-2</p> <p>Multiple security vulnerabilities affect the airflow-2 package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-an24336 https://cve.radiocsirt.org/vuln/euvd-2026-270470 EUVD-2026-270470 https://cve.radiocsirt.org/vuln/euvd-2026-270470 https://cve.radiocsirt.org/vuln/fkie_cve-2026-27205 <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-27205 https://cve.radiocsirt.org/vuln/ghsa-68rp-wp8r-4726 <p><strong>Affected:</strong> PyPI: flask</p> <p>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.</p> <p>The severity depends on the application&#39;s use of the session, and the cache&#39;s behavior regarding cookies. The risk depends on all these conditions being met.</p> <p>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.</p> <p><strong>Affected:</strong> PyPI: flask</p> <p>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.</p> <p>The severity depends on the application&#39;s use of the session, and the cache&#39;s behavior regarding cookies. The risk depends on all these conditions being met.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-68rp-wp8r-4726 https://cve.radiocsirt.org/vuln/oesa-2026-2135 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: python-flask</p> <p>Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks. Security Fix(es):</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&amp;apos;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.(CVE-2026-27205)</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: python-flask</p> <p>Flask is a lightweight WSGI web application framework. It is designed to make getting started quick and easy, with the ability to scale up to complex applications. It began as a simple wrapper around Werkzeug and Jinja and has become one of the most popular Python web application frameworks. Security Fix(es):</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&amp;apos;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.(CVE-2026-27205)</p> https://cve.radiocsirt.org/vuln/oesa-2026-2135 https://cve.radiocsirt.org/vuln/opensuse-su-2026:10264-1 <p>python311-Flask-3.1.3-1.1 on GA media</p> <p>python311-Flask-3.1.3-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:10264-1 https://cve.radiocsirt.org/vuln/pysec-2026-2151 <p><strong>Affected:</strong> PyPI: flask</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> <p><strong>Affected:</strong> PyPI: flask</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> https://cve.radiocsirt.org/vuln/pysec-2026-2151 https://cve.radiocsirt.org/vuln/suse-su-2026:22023-1 <p>Security update for python-Flask</p> <p>Security update for python-Flask</p> https://cve.radiocsirt.org/vuln/suse-su-2026:22023-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27205 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: flask, Ubuntu:18.04:LTS: flask, Ubuntu:Pro:20.04:LTS: flask, Ubuntu:22.04:LTS: flask, Ubuntu:24.04:LTS: flask, Ubuntu:25.10: flask</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: flask, Ubuntu:18.04:LTS: flask, Ubuntu:Pro:20.04:LTS: flask, Ubuntu:22.04:LTS: flask, Ubuntu:24.04:LTS: flask, Ubuntu:25.10: flask</p> <p>Flask is a web server gateway interface (WSGI) web application framework. In versions 3.1.2 and below, when the session object is accessed, Flask should set the Vary: Cookie header., resulting in a Use of Cache Containing Sensitive Information vulnerability. The logic 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 and risk depend on the application being hosted behind a caching proxy that doesn&#39;t ignore responses with cookies, not setting a Cache-Control header to mark pages as private or non-cacheable, and accessing the session in a way that only touches keys without reading values or mutating the session. The issue has been fixed in version 3.1.3.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27205 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2451 <p>Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Siebel CRM ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.</p> <p>Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Siebel CRM ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2451