apache-airflow
Affected
- introduced
0, fixed3.3.1(ecosystem)
Fixed versions
3.3.1
Fix
- Fixed version
3.3.1pip install --upgrade apache-airflow==3.3.1
Advisory
Also known as: BIT-airflow-2026-68971, CVE-2026-68971, PYSEC-2026-3994
Apache Airflow missing team context permits cross-team Dag actions and XCom reads
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.
Medium Basis: The source's own band: MODERATE
0, fixed 3.3.1 (ecosystem)3.3.1
3.3.1pip install --upgrade apache-airflow==3.3.1Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0