https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:04:17 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-369577 EUVD-2026-369577 https://cve.radiocsirt.org/vuln/euvd-2026-369577 https://cve.radiocsirt.org/vuln/fkie_cve-2026-68868 <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-68868 https://cve.radiocsirt.org/vuln/ghsa-qfr4-ppjq-9gr3 <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> https://cve.radiocsirt.org/vuln/ghsa-qfr4-ppjq-9gr3 https://cve.radiocsirt.org/vuln/pysec-2026-3714 <p><strong>Affected:</strong> PyPI: apache-airflow-providers-google</p> <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> <p><strong>Affected:</strong> PyPI: apache-airflow-providers-google</p> <p>The Google Cloud Secret Manager secrets backend in Apache Airflow&#39;s Google provider never applied the team scope when resolving Connections and Variables: the caller&#39;s `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team&#39;s Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.</p> https://cve.radiocsirt.org/vuln/pysec-2026-3714 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2823 <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2823