Apache says a party able to write to the Celery broker can submit a forged callback workload and run arbitrary code on CeleryExecutor workers without Airflow credentials.The broker-write condition is essential to exposure; the record does not describe an unrestricted internet-facing entry point. Teams can use a vulnerability intelligence platform to track which Airflow deployments use CeleryExecutor and need the 3.4.0 fix.
What it allows
How Does CVE-2026-68982 Reach a CeleryExecutor Worker?
Airflow uses ExecuteCallback workloads for deadline-alert callbacks, according to Apache's CVE record. Before the fix, a CeleryExecutor worker ran those workloads without validating their authentication token. A party with write access to the Celery broker could therefore enqueue a forged callback.
The worker could then execute arbitrary code without the attacker holding Airflow credentials. That is the stated consequence, not evidence that a particular deployment was compromised. For context, see the remote code execution definition.
What Does the Available Risk Evidence Mean?
Apache describes the severity as important. CISA ADP supplies a separate, secondary CVSS 3.1 score of 9.8 Critical; that number is not an Apache CNA score. CISA's November 13, 2026 KEV catalog did not list this CVE.
A November 14, 2026 GitHub repository-name search returned two public repositories bearing the CVE ID. Repository names alone do not verify exploit functionality, active exploitation, or an incident.
Who is affected
Which Airflow Deployments Need the CVE-2026-68982 Fix?
Apache's CVE record lists Apache Airflow versions before 3.4.0 as affected. The described execution path applies to deployments using CeleryExecutor, where an attacker can write to the Celery broker. The affected package in the CNA record is apache-airflow-core.
Check the running Airflow version and the configured executor for each deployment. Then review which users and services can publish to its Celery broker. Treat broker write access as the exposure condition, even when the Airflow web interface is separately authenticated.
How Should Teams Patch and Verify?
Apache advises upgrading to apache-airflow 3.4.0 or later. In that release, the worker claims the callback through the Execution API, which validates the token before the callback runs. Plan the upgrade for CeleryExecutor environments with broker write paths first.
After updating, verify that every running Airflow component reports version 3.4.0 or later. Confirm the deployment still uses the intended executor and restrict broker publishing to authorized services. Record the result in the patch management process; these checks are Brandefense defensive guidance.
Timeline
- 2026-11-09
Apache published the CVE record and advised upgrading to Airflow 3.4.0 or later.
- 2026-11-13
CISA ADP added its secondary CVSS 3.1 assessment to the CVE record.
What to do
-
Identify affected CeleryExecutor deployments
Record the running Apache Airflow version and executor configuration for each environment. Prioritize CeleryExecutor deployments running before 3.4.0.
-
Review Celery broker write access
Identify accounts and services that can publish workloads to each Celery broker. Reduce unnecessary write access while the affected deployment is upgraded.
-
Upgrade Apache Airflow
Follow Apache's advice to move affected deployments to apache-airflow 3.4.0 or later. Include all CeleryExecutor workers in the maintenance plan.
-
Verify the fix and investigate anomalies
Check that running components report version 3.4.0 or later. Review broker publishing and worker activity for unexpected callbacks; Apache's record provides no specific detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-68982 in Brandefense Atlas
The Atlas record of CVE-2026-68982: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-68982 require Airflow credentials?
Apache says an attacker with Celery broker write access can trigger the flaw without Airflow credentials. Broker write access remains a required condition.
Which Airflow version fixes the callback flaw?
Apache advises upgrading to apache-airflow 3.4.0 or later. Verify the running version across CeleryExecutor workers after maintenance.
Does the 9.8 score come from Apache?
No. Apache labels the issue important without a numeric CVSS score. CISA ADP separately assigns a secondary CVSS 3.1 score of 9.8 Critical.
Does discussion of the CVE establish active exploitation?
No. A November 14, 2026 GitHub repository-name search returned two public repositories bearing the CVE ID. Repository names alone do not establish a working exploit or incident.
Sources
- CVE-2026-68982 Apache CNA RecordApache Software Foundation via CVE Program
- Known Exploited Vulnerabilities CatalogCISA