https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 23:50:48 +0000 https://cve.radiocsirt.org/vuln/bit-airflow-2025-57735 <p><strong>Affected:</strong> Bitnami: airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> <p><strong>Affected:</strong> Bitnami: airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> https://cve.radiocsirt.org/vuln/bit-airflow-2025-57735 https://cve.radiocsirt.org/vuln/euvd-2026-290286 EUVD-2026-290286 https://cve.radiocsirt.org/vuln/euvd-2026-290286 https://cve.radiocsirt.org/vuln/fkie_cve-2025-57735 <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-57735 https://cve.radiocsirt.org/vuln/ghsa-c92r-g8j5-vhcx <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> https://cve.radiocsirt.org/vuln/ghsa-c92r-g8j5-vhcx https://cve.radiocsirt.org/vuln/pysec-2026-269 <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>When user logged out, the JWT token the user had authtenticated with was not invalidated, which could lead to reuse of that token in case it was intercepted. In Airflow 3.2 we implemented the mechanism that implements token invalidation at logout. Users who are concerned about the logout scenario and possibility of intercepting the tokens, should upgrade to Airflow 3.2+</p> <p>Users are recommended to upgrade to version 3.2.0, which fixes this issue.</p> https://cve.radiocsirt.org/vuln/pysec-2026-269 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1042 <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen und vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen und vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1042