Apache Airflow security note

What changed

• CVE-2026-45426 — Check if you run it

  Exploitation requires the attacker to already be an authenticated Airflow worker holding a valid Log-server JWT issued for at least one Dag.

  Affected < 3.2.2

• CVE-2026-42360 — Check if you run it

  A bug in Apache Airflow's rendered-template field handling caused nested sensitive-key masking (e.g.

  Affected < 3.2.2

• CVE-2026-42252 — Check if you run it

  Apache Airflow's official documentation at ("Passing Parameters when triggering Dags") showed a verbatim example without any quoting / sanitization warning.

  Affected < 3.2.2

• CVE-2026-41014 — Check if you run it

  The partitioned_dag_runs endpoints in the Airflow UI enforced only asset-level access control, not per-Dag authorization.

  Affected < 3.2.2

• CVE-2026-40963 — Check if you run it

  The structure_data endpoint in the Airflow UI returned external dependency graph nodes for linked Dags without checking whether the caller had read permission on those linked Dags.

  Affected < 3.2.2

• CVE-2026-40961 — Check if you run it

  sync 2026-11-02T23:08:20Z

  Affected < 3.2.2

• CVE-2026-40861 — Check if you run it

  A Dag author could either (a) create a symlink under their task's log directory pointing to an arbitrary file readable by the API server process (read-path attack — e.g.

  Affected < 3.2.2

• CVE-2026-33858 — Check if you run it

  Dag Authors, who normally should not be able to execute code in the webserver context could craft XCom payload causing the webserver to execute arbitrary code.

  Affected < 3.2.0

What we still do not know

Every changed record in this note has a version range.