Quick answers
- Is CVE-2026-68982 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68982 being exploited in the wild.
- How severe is CVE-2026-68982?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow before 3.4.0.
- Is there a fix for CVE-2026-68982?
- Yes: fixed in apache-airflow 3.4.0 or later. Until then: Restrict network access to the Celery broker to prevent unauthorized message injection; only trusted services should be able to enqueue tasks and callbacks. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-68982 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-68982?
- Check whether you run Apache Airflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: apache-airflow 3.4.0 or later
Restrict network access to the Celery broker to prevent unauthorized message injection; only trusted services should be able to enqueue tasks and callbacks.
Technical details
The CeleryExecutor ran callback workloads (ExecuteCallback) without validating authentication tokens before execution. An attacker with access to the Celery broker could enqueue forged callbacks that are executed on worker machines. The fix introduces a new POST endpoint in the Execution API that validates the callback token and atomically transitions the callback state from QUEUED to RUNNING before execution, mirroring the protection model already used for connection tests.
Affected products
- Apache Airflow before 3.4.0
Timeline
- 2026-11-09: disclosed
- 2026-08-01: patched: Fix merged in PR #70927 for Airflow 3.4.0