CVE-2026-68982
Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validation
No known exploitation. EPSS puts it in the 53rd percentile. Fixed in 3.4.0.
No public exploit knownFix3.4.0Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.0.196486
What to do
Find your product and version, then upgrade to the build on the right.
- Apache Software Foundation Apache AirflowAffected: < 3.4.0Upgrade to: 3.4.0Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check whether your Airflow deployment uses the CeleryExecutor (not LocalExecutor or KubernetesExecutor).
- Check whether anything untrusted can write to your Celery message broker (e.g. network exposure, shared credentials).
- Upgrade Apache Airflow to version 3.4.0 or later, which validates the workload token before running callbacks.
- After upgrading, restrict network and credential access to the Celery broker as a defense-in-depth measure.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordA flaw in Apache Airflow's task-scheduling system lets someone who can write to its internal message queue run their own code on your workers without needing a login; there's no sign it's being actively exploited yet, but if you use this setup you should update soon.
CeleryExecutor deployments of Apache Airflow execute ExecuteCallback workloads without validating the workload authentication token, letting anyone able to write to the Celery broker enqueue a forged callback for unauthenticated remote code execution on every worker (CWE-306).
If you're affected
- Full worker takeover
- Arbitrary code execution
- Data pipeline tampering
- Operational disruption
- Lateral movement into infrastructure
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.7% chance of exploitation activity in the next 30 days, which ranks it in the 53rd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
- Attention now
Sustained, driven by wide press coverage.
Lifecycle
9 events over 4 days, from the signal feeds we watch.
- Record updated
- OpenVAS check addedrecord updated
- Record updated
- Publishedweakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 9.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Apache Airflow, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI