https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 00:51:13 +0000 https://cve.radiocsirt.org/vuln/bit-airflow-2026-41084 <p><strong>Affected:</strong> Bitnami: airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> <p><strong>Affected:</strong> Bitnami: airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> https://cve.radiocsirt.org/vuln/bit-airflow-2026-41084 https://cve.radiocsirt.org/vuln/cleanstart-2026-bm42810 <p><strong>Affected:</strong> CleanStart: airflow-3</p> <p>Security vulnerability affects the airflow-3 package. This issue is resolved in later releases. See references for vulnerability details.</p> <p><strong>Affected:</strong> CleanStart: airflow-3</p> <p>Security vulnerability affects the airflow-3 package. This issue is resolved in later releases. See references for vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-bm42810 https://cve.radiocsirt.org/vuln/euvd-2026-324047 EUVD-2026-324047 https://cve.radiocsirt.org/vuln/euvd-2026-324047 https://cve.radiocsirt.org/vuln/fkie_cve-2026-41084 <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-41084 https://cve.radiocsirt.org/vuln/ghsa-mxq5-f9c5-w4p5 <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> https://cve.radiocsirt.org/vuln/ghsa-mxq5-f9c5-w4p5 https://cve.radiocsirt.org/vuln/pysec-2026-183 <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>A bug in Apache Airflow&#39;s bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path while operating on the `dag_id` / `dag_run_id` extracted from request-body entity fields. An authenticated UI/API user with edit permission on one Dag could mutate Task Instance state in any other Dag by keeping the authorized Dag&#39;s ID in the URL path and naming the target Dag&#39;s IDs in the request body entities. Affects deployments that rely on per-Dag edit-scope to keep Task Instance state isolated between teams. Users are advised to upgrade to `apache-airflow` 3.2.2 or later.</p> https://cve.radiocsirt.org/vuln/pysec-2026-183 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1761 <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um Dateien zu manipulieren, und um Sicherheitsvorkehrungen zu umgehen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1761