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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 09 Nov 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validation | |
| Weaknesses | CWE-306 | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2026-11-09T09:55:00.238Z
Reserved: 2026-08-02T00:09:01.550Z
Link: CVE-2026-68982
No data.
Status : Received
Published: 2026-11-09T10:17:11.123
Modified: 2026-11-09T10:17:11.123
Link: CVE-2026-68982
No data.
OpenCVE Enrichment
No data.
-
CWE-306
Missing Authentication for Critical Function