Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validation
cve-program · CVE-2026-68982 · Published
No access to your tenant or devices. Every item links to its source. What this means
Historical advisory recorded 13 Nov 2026 18:56:54 UTC. Read the latest advisory.
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.
Read the publisher's advisorySee how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
cve-program · CVE-2026-68982 · Published
cve-program · CVE-2026-68982 · Published
cve-program · CVE-2026-68982 · Published
cve-program · CVE-2026-68982 · Published
This historical link shows only this version and versions saved before it. Browse all advisory history.