Executive brief
Apache Airflow, a platform used to programmatically author and schedule workflows, contains a vulnerability that could allow users to view sensitive source code they are not authorized to see. If multiple workflows (DAGs) are stored in the same file, a user with permission to view just one of those workflows can see the entire file, including the code for other workflows. This could lead to the exposure of proprietary business logic or sensitive configuration details contained within the code.
Technical details
An authorization bypass vulnerability exists in Apache Airflow's DAG source viewing functionality. The `GET /api/v2/dagSources/{dag_id}` endpoint and the corresponding UI view fail to redact or restrict the returned source code to only the authorized DAG when multiple DAGs are co-located in a single source file. An attacker with low-privileged read access to at least one DAG in a shared file can exploit this to disclose the source code of all other DAGs in that same file, bypassing per-DAG access control lists (ACLs). This issue is resolved in version 3.3.0 by ensuring proper redaction or access enforcement for co-located DAGs.
Affected products
- Apache apache-airflow < 3.3.0
Timeline
- 2026-07-07: advisory: GitHub Advisory published
- 2026-07-07: disclosed: NVD publication date
- 3.3.0: patched: First patched version