Advisory

GHSA-5247-m8w9-2v4m

Also known as: BIT-airflow-2026-68971, CVE-2026-68971, PYSEC-2026-3994

Summary

Apache Airflow missing team context permits cross-team Dag actions and XCom reads

Details

Apache Airflow's asset materialization endpoint (POST /api/v2/assets/{asset_id}/materialize) and the XCom result check on wait_dag_run_until_finished authorized the target Dag without its team, unlike every other authorization site. A team-aware auth manager distinguishes a team-scoped Dag from a global one by that field -- the Keycloak auth manager, for example, checks the DAG resource instead of DAG:<team> -- so the team-scoped permission that should gate the request was never consulted. In a deployment running multi-team mode with a team-aware auth manager, an authenticated user in one team could trigger Dag runs belonging to another team, supplying their own dag_run_id and conf, and could read another team's XCom values. Deployments using the FAB auth manager are unaffected, as it has no multi-team support. Users are advised to upgrade to apache-airflow 3.3.1 or later, which resolves the Dag's team at both sites.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-08-12 18:31 UTC
Modified
2026-10-02 23:40 UTC

Affected packages and fixes

apache-airflow

PyPI · All systems

Affected

  • introduced 0, fixed 3.3.1 (ecosystem)

Fixed versions

3.3.1

Fix

  • Fixed version 3.3.1
    pip install --upgrade apache-airflow==3.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences