Skip to main content
CVE-2026-68982VulnerabilityPublished

Apache Airflow's CeleryExecutor ran callback workloads (ExecuteCallback, used for deadline-alert callbacks) without

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-68982· High

Not known to be exploited : upgrade to 3.4.0 soon.

Data as of 9 Nov 2026, 13:21 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.4.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Airflow and apache-airflow-core to 3.4.0.

Affected software

ProductAffectedFixed in
Apache Airflowapache-airflow-coreAffected
  • <3.4.0
Fixed in
  • 3.4.0
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • <3.4.0
Fixed in
  • 3.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Airflow to version 3.4.0 or later, where the CeleryExecutor worker validates authentication tokens before executing callbacks. This official fix prevents unauthorized execution of callback workloads. Until upgraded, deployments remain vulnerable if the Celery broker is accessible for unauthorized writes.

Description

Apache Airflow's CeleryExecutor component allowed execution of callback workloads without validating authentication tokens. This flaw enables an attacker with write access to the Celery broker to enqueue forged callbacks that execute arbitrary code on all CeleryExecutor workers without needing Airflow credentials. The issue affects deployments using the CeleryExecutor. A fix is available in Apache Airflow version 3.4.0 and later, where token validation is enforced before executing callbacks.

References

Community reviews

Loading reviews…