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, un
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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Python (PyPI) | apache-airflow | < 3.3.1 | 3.3.1 |
Referencias
- https://nvd.nist.gov/vuln/detail/CVE-2026-68971
- https://github.com/apache/airflow/pull/70893
- https://github.com/apache/airflow/commit/0940c4b66c270d929e9f59914c65e15bd4734680
- https://github.com/apache/airflow/commit/f81459835adb111e57b2a87f586d856395660f8a
- https://github.com/apache/airflow
- https://github.com/apache/airflow/releases/tag/3.3.1
- https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2026-3994.yaml
- https://lists.apache.org/thread/kfxqqwgojdjdnt6bxg3ord4y41y334fo
- http://www.openwall.com/lists/oss-security/2026/08/12/15
- https://github.com/advisories/GHSA-5247-m8w9-2v4m
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Debilidad (CWE)
CWE-862- Plataforma
- Python (PyPI)
- Paquete
apache-airflow- Publicada
- 12.08.2026
- Actualizado
- 15.10.2026 18:17
Fuentes y licencias
OSV / GitHub Advisory Database - PYSEC-2026-3994 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-5247-m8w9-2v4m - CC BY 4.0
Historial de vulnerabilidades: apache-airflow
Todas las vulnerabilidades publicadas de este paquete (Python (PyPI)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 158
- Primera → última
- 08.2018 09.2026
- Sin corrección
- 4
- Explotada en ataques
- 2
Distribución por gravedad
- Crítica 16
- Alta 49
- Media 86
- Baja 7
Divulgaciones por año
- 2018: 1
- 2019: 8
- 2020: 12
- 2021: 5
- 2022: 16
- 2023: 31
- 2024: 18
- 2025: 6
- 2026: 61
-
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, un esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.