Skip to main content
Menu
CVEs

Apache Airflow Core unauthenticated code execution in CeleryExecutor

CVE-2026-68982EUVD-2026-119905GHSA-3M38-QXXM-8G9GPublished November 9, 2026, updated Needs attention

9.8CriticalCISA-ADP
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in 3.4.0
Who is exposed
Not reported

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.

Written by a model

Original 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

Upgrade to a fixed version: 3.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-68982 (Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-68982 (entry last updated 2026-11-13):
Affected:
- PyPI package apache-airflow-core: fixed in 3.4.0
Fixed versions: 3.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-68982 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68982 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/7t514l87nhjworv2ns22b8ltxr1f7rhg
- https://github.com/apache/airflow/pull/71192
- https://github.com/apache/airflow/pull/70927
- https://www.cve.org/CVERecord?id=CVE-2020-11981
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-68982
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68982"}.

Affected versions

cve.now Index

64of 100 · methodology v3
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach12/20apache-airflow-core: 636.5K downloads a week
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 87 if added to CISA KEV
  • Would score about 82 if CISA's SSVC rates exploitation active
  • Would score about 69 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now4 days
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now1 day
  6. Exploit code on GitHub

    im0xfay/CVE-2026-68982

Public exploit activity

20Posted on X by cve.now100%0Nov 9Nov 22
  • GitHub PoC repos: 2
  • EPSS: 0.91%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 6

Evidence 8

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Advisorylists.apache.org · thread.html/7t514l87nhjworv2ns22b8ltxr1f7rhg
CVE record 3Establishes: The identifier and description.
RecordCVE List · CVE-2026-68982
RecordNVD · CVE-2026-68982
Linkcve.org · CVERecord?id=CVE-2020-11981
Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · Ghost-Bx1/cve-2026-68982-airflow-celery-rce · Repository
ExploitGitHub · im0xfay/CVE-2026-68982 · Repository
Other links 2
PatchGitHub · apache/airflow · Pull request #71192
PatchGitHub · apache/airflow · Pull request #70927

Questions about CVE-2026-68982

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. Public exploit code exists (a proof of concept on GitHub).

Source: cve.now feed data

Which versions are affected by CVE-2026-68982?

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

Source: cve.now feed data

How do I fix CVE-2026-68982?

Upgrade to a fixed version: 3.4.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.