Apache Airflow's official documentation previously included an example of BashOperator usage that directly embedded user-supplied parameters from dag_run.conf into a shell command without quoting or sanitization. This allowed authenticated users with DAG trigger permissions to inject shell metacharacters via the conf field, potentially executing arbitrary commands on the worker node. The issue is due to unsafe documentation patterns rather than a direct software flaw. The documentation was corrected in Apache Airflow 3.2.2 to include proper shell quoting and warnings about this risk. Deployments that copied the vulnerable pattern are at risk until they update their DAG code or upgrade to the fixed documentation version. This vulnerability is similar to prior documentation-related issues (CVE-2025-50213, CVE-2025-27018) involving unsafe template usage.

An authenticated user with permission to trigger DAG runs could exploit this issue by injecting shell commands through the conf parameter, leading to arbitrary command execution on the Airflow worker. This could compromise the worker environment and potentially affect the broader system depending on deployment context. The impact is limited to deployments that implemented DAGs based on the vulnerable documentation example without applying proper input sanitization or quoting.

Users should upgrade to Apache Airflow version 3.2.2 or later to obtain the corrected documentation that includes explicit shell quoting and safety warnings. Additionally, DAG authors should review and update any DAG code modeled on the vulnerable example to ensure that user-supplied parameters are properly quoted or sanitized before being passed to shell commands. Since this is primarily a documentation issue, no direct software patch is indicated beyond upgrading to receive the fixed docs. No further action is required if the deployment does not use the vulnerable pattern or if input sanitization is already implemented.