Średnia

Before apache-airflow 3.3.0, a user authorized to read one Dag could disclose the source of other Dags co-located in the same source file. `GET /api/v2/dagSources/{dag_id}` — and the equivalent Dag-so

Ujawniono: 07.07.2026
Aktualizacja: 11.10.2026 14:19

Before apache-airflow 3.3.0, a user authorized to read one Dag could disclose the source of other Dags co-located in the same source file. GET /api/v2/dagSources/{dag_id} — and the equivalent Dag-source view in the UI — returned the entire source file without redacting Dags the caller was not authorized to read, bypassing per-DAG read authorization. Deployments that co-locate multiple Dags in a single file and rely on per-DAG access control to limit source visibility are affected; single-Dag-per-file deployments are not. Upgrade to apache-airflow 3.3.0 or later.

Czego dotyczy

Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.

Platforma	Paczka	Podatne wersje	Poprawka w wersji
Python (PyPI)	apache-airflow	< 3.3.0	3.3.0

Odnośniki

Ocena CVSS 6.5/10

Wektor CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Słabość (CWE): CWE-639
Platforma: Python (PyPI)
Paczka: apache-airflow
Ujawniono: 07.07.2026
Aktualizacja: 11.10.2026 14:19

Źródła i licencje

OSV / GitHub Advisory Database - GHSA-4fh7-7jx4-8f6c - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-2083 - PyPA Advisory Database; CC BY 4.0

Historia podatności: apache-airflow

Wszystkie opisane podatności tej paczki (Python (PyPI)), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.

Wszystkie (158) w archiwum

Wszystkich wpisów: 158
Pierwsza → ostatnia: 08.2018 09.2026
Bez poprawki: 4
Wykorzystywana w atakach: 2

Rozkład istotności

Krytyczna 16
Wysoka 49
Średnia 86
Niska 7

Ujawnienia w latach

2018: 1
2019: 8
2020: 12
2021: 5
2022: 16
2023: 31
2024: 18
2025: 6
2026: 61

21.09.2026

Apache Airflow: the Core API logout endpoint revokes only a session token presented as the _token cookie. When a client logs out presenting its credential as an Authorization bearer header instead, th

Krytyczna · 9.1 CVE-2026-86473 >= 3.0.0, < 3.3.2 3.3.2
12.08.2026

Apache Airflow's Backfill API authorized a request against a Dag id supplied by the caller whenever the `backfill_id` path segment failed to parse. The authorization dependency parsed it with `int()`

Wysoka · 7.5 CVE-2026-68968 < 3.3.1 3.3.1
12.08.2026

Apache Airflow's Task SDK rebuilt a `Callback` object from serialized data by re-running its constructor, which imports the module named by the stored callback path. Because `SyncCallback` is itself a

Wysoka · 8.8 CVE-2026-67587 >= 3.3.0, < 3.3.1 3.3.1
12.08.2026

Apache Airflow 3.3.0 moved human-in-the-loop tasks from the triggerer to a new `awaiting_input` task state swept by the scheduler. That sweep deserializes the task instance's `next_kwargs` without an

Wysoka · 7.3 CVE-2026-67260 >= 3.3.0, < 3.3.1 3.3.1
12.08.2026

Apache Airflow's serialization layer reconstructed exception nodes by calling `import_string()` on a class name taken from the serialized blob and instantiating it with arguments from the same blob, w

Wysoka · 8.8 CVE-2026-58076 >= 3.3.0, < 3.3.1 3.3.1
07.07.2026

Before apache-airflow 3.3.0, a user authorized to read one Dag could disclose the source of other Dags co-located in the same source file. `GET /api/v2/dagSources/{dag_id}` — and the equivalent Dag-so ten wpis

Średnia · 6.5 CVE-2026-49296 < 3.3.0 3.3.0
07.07.2026

A bug in `BaseSerialization.deserialize()` allowed unrestricted `import_string()` of attacker-controlled class paths when the Scheduler / API Server loaded a serialized DAG: a DAG author could embed a

Krytyczna · 9.8 CVE-2026-33264 < 3.3.0 3.3.0
01.06.2026

A bug in Apache Airflow's XCom PATCH endpoint `PATCH /api/v2/xcomEntries/{key}` allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e

Wysoka · 8.8 CVE-2026-42359 >= 3.2.0, < 3.2.2 3.2.2
01.06.2026

A bug in Apache Airflow's bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path whil

Wysoka · 7.5 CVE-2026-41084 >= 3.2.0, < 3.2.2 3.2.2
01.06.2026

Apache Airflow's official documentation at `core-concepts/dag-run.html` ("Passing Parameters when triggering Dags") showed a verbatim `BashOperator(bash_command="echo value: {{ dag_run.conf['conf1'] }

Krytyczna · 9.1 CVE-2026-42252 >= 3.0.0, < 3.2.2 3.2.2
01.06.2026

Apache Airflow: Authenticated users can bypass the `is_safe_url` check

Wysoka · 7.2 CVE-2026-40961 < 3.2.2 3.2.2
01.06.2026

Apache Airflow Vulnerable to Deserialization of Untrusted Data

Wysoka · 7.3 CVE-2026-45360 >= 3.2.0, < 3.2.2 3.2.2
18.04.2026

Apache Airflow allows code execution through crafted XCom payloads

Wysoka · 7.2 CVE-2026-25917 < 3.2.0 3.2.0
16.04.2026

Apache Airflow: JWT token appearing in logs

Wysoka · 7.5 CVE-2026-31987 >= 3.0.0, < 3.2.0 3.2.0
16.04.2026

Apache Airflow: RCE by race condition in example_xcom dag

Wysoka · 8.1 CVE-2025-54550 < 3.2.0 3.2.0
13.04.2026

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. Since Dag Authors are already highly tru

Wysoka · 8.8 CVE-2026-33858 >= 3.1.8, < 3.2.0 3.2.0
09.04.2026

Apache Airflow: JWT token still valid after logout

Krytyczna · 9.1 CVE-2025-57735 >= 3.0.0, < 3.2.0 3.2.0
17.03.2026

Apache Airflow versions 3.1.0 through 3.1.7 missing authorization vulnerability in the Execution API's Human-in-the-Loop (HITL) endpoints that allows any authenticated task instance to read, approve,

Wysoka · 8.1 CVE-2026-30911 >= 3.1.0, < 3.1.8 3.1.8
17.03.2026

Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url.

Wysoka · 7.5 CVE-2026-28779 >= 3.0.0, < 3.1.8 3.1.8
24.02.2026

Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table

Wysoka · 8.4 CVE-2024-56373 < 2.11.1 2.11.1

Pokaż więcej (20) Widać 20 z 66

Dowiedz się, które podatności dotyczą Twojej aplikacji

Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.

Podłącz swoją aplikację