GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow CeleryExecutor: forged callbacks from the Celery broker run arbitrary code on workers

UnscoredCVE-2026-68982Control plane, storage & DevOpscurated

Impact

CeleryExecutor workers ran ExecuteCallback workloads (used for deadline-alert callbacks) without validating the workload's authentication token. Anyone who can write to the Celery broker can enqueue a forged callback and run arbitrary code on every CeleryExecutor worker, with no Airflow credentials. Workers usually hold the connection credentials and network reach of every pipeline they run, so this gives an attacker those credentials and that network access across the fleet. The real exposure depends on how well the broker (Redis/RabbitMQ) is locked down.

Who can reach it

Anyone with write access to the Celery broker used by Airflow. No Airflow authentication is needed. Only deployments using the CeleryExecutor are affected.

What to do

Upgrade to apache-airflow 3.4.0 or later and restart the scheduler and all Celery workers. In 3.4.0 the worker claims the callback through the Execution API, which validates the token, before running it. Until then, make sure the broker requires authentication and only Airflow components can reach it.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.