Deployments running Apache Airflow 3.0.5 through versions before 3.4.0 are exposed only if example Dags are loaded. Exploitation also requires a user who can trigger the example_dag_decorator Dag with a custom url parameter.
The attacker needs to provide a custom URL for the Dag and have that URL return an IP address containing an IPv6 zone identifier with injected shell-command characters. The resulting command executes on the Airflow worker.
The vulnerable code is in an example Dag, so deployments with load_examples disabled are not affected through this path. Disabling example Dags is recommended for production.
Set load_examples = False to prevent the example Dags from being loaded. The advised permanent remediation is upgrading to Apache Airflow 3.4.0 or later.
No. This issue is described as an incomplete fix for CVE-2025-54941, and users who upgraded for that CVE need to upgrade again to Apache Airflow 3.4.0 or later.