Skip to main content
← Vulnerabilities

Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validation

Exploited
No known exploitation
Fix
Fixed in 3.4.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.4.0.

Published
Last modified
12/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Apache Airflow's CeleryExecutor runs callback workloads without checking their authentication token, so anyone who can write to the Celery broker can queue a forged callback and run arbitrary code on every CeleryExecutor worker, without Airflow credentials. Only deployments that use the CeleryExecutor are affected.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original 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.

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach12/20apache-airflow-core: 647K downloads a week
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Impact

  • Widely used

    apache-airflow-core has 647k weekly downloads.Source: pypistats.org

    473 packages depend on apache-airflow-core.Source: deps.dev

What to do

  • Upgrade to a fixed version: 3.4.0.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • fixed in 3.4.0

    Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).

    The latest release, 3.4.0, is not affected.

Evidence 4

  1. Advisory
  2. Patch
  3. Patch
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-68982

Is CVE-2026-68982 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-68982?

apache-airflow-core (PyPI): before 3.4.0.Source: cve.now feed data

How do I fix CVE-2026-68982?

Upgrade to a fixed version: 3.4.0.Source: cve.now feed data