CVE-2026-68982 · Runtime
NO FIX YET · SEE WHAT TO DO
Apache Airflow's CeleryExecutor runs callback workloads without checking their authentication token. Anyone who can write to the Celery broker can enqueue a forged callback and execute arbitrary code on every CeleryExecutor worker, without Airflow credentials.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Deployments that run Apache Airflow with the CeleryExecutor are exposed, since every Celery worker runs the forged callback. Exposure depends on who can write to the Celery broker; anyone who can only reach the Airflow web interface without broker access is not described as affected by the sources. Deployments using other executors are not affected according to the sources.
Not affected if non-celery-executor
Who cares apache-airflow, celery, python, self-hosted
executor setting in airflow.cfg or the AIRFLOW__CORE__EXECUTOR environment variable.airflow version; versions before 3.4.0 are affected.3.4.0 or later, in which the worker validates the token before running a callback.Apache Airflow's CeleryExecutor ran callback workloads (ExecuteCallback, used for deadline-alert callbacks) without validating the workload's authentication token. Anyone able to write to the Celery broker could enqueue a forged callback and execute arbitrary code on every CeleryExecutor worker, without Airflow credentials. Deployments using the CeleryExecutor are affected.
Users are advised to upgrade to apache-airflow 3.4.0 or later, in which the worker claims the callback through the Execution API, validating the token, before running it.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.