---
id: "CVE-2026-68982"
page: "https://infrastack.ai/live/CVE-2026-68982"
kind: "vulnerability"
aliases: ["CVE-2026-68982"]
title: "Apache Airflow: forged Celery callbacks let broker writers run code on workers"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["apache-airflow", "celery", "python", "runtime", "self-hosted"]
not_affected_if: ["non-celery-executor"]
published_at: "2026-11-09T10:17:11+00:00"
first_seen_at: "2026-11-09T10:25:49+00:00"
updated_at: "2026-11-09T10:26:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68982", "first_seen_at": "2026-11-09T10:25:49+00:00"}]
exploit_sources: []
---

# Apache Airflow: forged Celery callbacks let broker writers run code on workers

Link for people: https://infrastack.ai/live/CVE-2026-68982 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the deployment uses the CeleryExecutor by reviewing the `executor` setting in `airflow.cfg` or the `AIRFLOW__CORE__EXECUTOR` environment variable.
- Check the installed Airflow version with `airflow version`; versions before `3.4.0` are affected.
- Check who can write to the Celery broker (for example Redis or RabbitMQ) and whether that access is restricted.

## Fix

- apache-airflow: upgrade to `3.4.0` or later, in which the worker validates the token before running a callback.

## Timeline

- 2026-11-09T10:25:49+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-68982

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_