The Apache Airflow project published CVE-2026-68982 on 9 November 2026, rating it important. Apache says Airflow's CeleryExecutor ran callback workloads (ExecuteCallback, used for deadline-alert callbacks) without validating the workload's authentication token, so anyone able to write to the Celery broker could enqueue a forged callback and execute arbitrary code on every CeleryExecutor worker, without Airflow credentials.

Apache says Airflow before 3.4.0 is affected on deployments using the CeleryExecutor, and that in 3.4.0 the worker claims the callback through the Execution API, validating the token, before running it. Apache credits Or Sahar (Reflectiz) as finder.

In Reflectiz's write-up of 9 November 2026, Or Sahar says he confirmed the flaw on Airflow 3.2.1 and 3.3.0 with a Redis broker, that the attack leaves no DagRun or TaskInstance in Airflow's UI or API, and that there is no earlier patched release than 3.4.0. (source: Apache Airflow; Reflectiz)