Zaloguj się
Deutsch English Español Polski
Wysoka

Apache Airflow: RCE by race condition in example_xcom dag

  • Ujawniono: 16.04.2026
  • Aktualizacja: 11.10.2026 14:18

The example example_xcom that was included in airflow documentation implemented unsafe pattern of reading value from xcom in the way that could be exploited to allow UI user who had access to modify XComs to perform arbitrary execution of code on the worker. Since the UI users are already highly trusted, this is a Low severity vulnerability.

It does not affect Airflow release - example_dags are not supposed to be enabled in production environment, however users following the example could replicate the bad pattern. Documentation of Airflow 3.2.0 contains version of the example with improved resiliance for that case.

Users who followed that pattern are advised to adjust their implementations accordingly.

Czego dotyczy

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

PlatformaPaczkaPodatne wersjePoprawka w wersji
Python (PyPI) apache-airflow < 3.2.0 3.2.0

Odnośniki

Ocena CVSS 8.1/10
Wektor CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Słabość (CWE)
CWE-94
Platforma
Python (PyPI)
Paczka
apache-airflow
Ujawniono
16.04.2026
Aktualizacja
11.10.2026 14:18

Źródła i licencje

OSV / GitHub Advisory Database - GHSA-q2hg-643c-gw8h - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-2353 - 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

Istotność:
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. Apache Airflow: Authenticated users can bypass the `is_safe_url` check
    Wysoka · 7.2 CVE-2026-40961 < 3.2.2 3.2.2
  11. Apache Airflow Vulnerable to Deserialization of Untrusted Data
    Wysoka · 7.3 CVE-2026-45360 >= 3.2.0, < 3.2.2 3.2.2
  12. Apache Airflow allows code execution through crafted XCom payloads
    Wysoka · 7.2 CVE-2026-25917 < 3.2.0 3.2.0
  13. Apache Airflow: JWT token appearing in logs
    Wysoka · 7.5 CVE-2026-31987 >= 3.0.0, < 3.2.0 3.2.0
  14. Apache Airflow: RCE by race condition in example_xcom dag ten wpis
    Wysoka · 8.1 CVE-2025-54550 < 3.2.0 3.2.0
  15. 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
  16. Apache Airflow: JWT token still valid after logout
    Krytyczna · 9.1 CVE-2025-57735 >= 3.0.0, < 3.2.0 3.2.0
  17. 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
  18. 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
  19. 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
  20. Apache Airflow proxy credentials for various providers might leak in task logs
    Wysoka · 7.5 CVE-2025-68675 >= 3.0.0b1, < 3.1.6, < 2.11.1 3.1.6, 2.11.1
  21. Apache Airflow secrets in rendered templates could contain parts of sensitive values when truncated
    Wysoka · 7.5 CVE-2025-68438 >= 3.1.0, < 3.1.6 3.1.6
  22. Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
    Krytyczna · 9.8 CVE-2025-67895 < 2.0.0 2.0.0
  23. Apache Airflow: Sensitive configuration values are not masked in the logs by default
    Wysoka · 7.5 CVE-2024-45784 < 2.10.3 2.10.3
  24. Apache Airflow vulnerable to Improper Encoding or Escaping of Output
    Wysoka · 8.8 CVE-2024-45498 >= 2.10.0, < 2.10.1 2.10.1
  25. Apache Airflow vulnerable to Execution with Unnecessary Privileges
    Wysoka · 8.8 CVE-2024-45034 < 2.10.1 2.10.1
  26. Apache Airflow has DAG Author Code Execution possibility in airflow-scheduler
    Wysoka · 8.8 CVE-2024-39877 >= 2.4.0, < 2.9.3 2.9.3
  27. Apache Airflow, versions before 2.8.1, have a vulnerability that allows a potential attacker to poison the XCom data by bypassing the protection of "enable_xcom_pickling=False" configuration setting r
    Wysoka · 7.5 CVE-2023-50943 < 2.8.1 2.8.1
  28. Apache Airflow, versions before 2.8.1, have a vulnerability that allows an authenticated user to access the source code of a DAG to which they don't have access. This vulnerability is considered low s
    Wysoka · 6.5 CVE-2023-50944 < 2.8.1 2.8.1
  29. Apache Airflow, versions before 2.7.3, has a vulnerability that allows an authorized user who has access to read specific DAGs only, to read information about task instances in other DAGs.  This is a
    Wysoka · 6.5 CVE-2023-42781 < 2.7.3 2.7.3
  30. Apache Airflow Celery provider Insertion of Sensitive Information into Log File vulnerability
    Wysoka · 7.5 CVE-2023-46215 >= 1.10.0, < 2.7.0 2.7.0
  31. Apache Airflow, versions before 2.7.1, is affected by a vulnerability that allows authenticated users who have access to see the task/dag in the UI, to craft a URL, which could lead to unmasking the s
    Wysoka · 6.5 CVE-2023-40712 < 2.7.1 2.7.1
  32. Apache Airflow, in versions prior to 2.7.0, contains a security vulnerability that can be exploited by an authenticated user possessing Connection edit privileges. This vulnerability allows the user t
    Wysoka · 8.1 CVE-2023-37379 < 2.7.0 2.7.0
  33. The session fixation vulnerability allowed the authenticated user to continue accessing Airflow webserver even after the password of the user has been reset by the admin - up until the expiry of the s
    Wysoka · 8.0 CVE-2023-40273 < 2.7.1rc1 2.7.1rc1
  34. apache-airflow-providers-apache-drill Improper Input Validation vulnerability
    Wysoka · 7.5 CVE-2023-39553 < 2.4.3 2.4.3
  35. Execution with Unnecessary Privileges, : Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Software Foundation Apache Airflow.The "Run Task" feature enables authentica
    Wysoka · 8.8 CVE-2023-39508 < 2.6.0 2.6.0
  36. Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an unauthorized actor to gain access to sensitive information in Connection edit view. This vulnerability is considere
    Wysoka · 6.5 CVE-2022-46651 < 2.6.3 2.6.3
  37. Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows unauthorized read access to a DAG through the URL. It is recommended to upgrade to a version that is not affected
    Wysoka · 6.5 CVE-2023-35908 < 2.6.3 2.6.3
  38. Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an attacker to cause a service disruption by manipulating the run_id parameter. This vulnerability is considered low s
    Wysoka · 6.5 CVE-2023-22888 < 2.6.3 2.6.3
  39. Apache Airflow, versions before 2.6.3, has a vulnerability where an authenticated user can use crafted input to make the current request hang. It is recommended to upgrade to a version that is not aff
    Wysoka · 6.5 CVE-2023-36543 < 2.6.3 2.6.3
  40. Apache Airflow, versions before 2.6.3, is affected by a vulnerability that allows an attacker to perform unauthorized file access outside the intended directory structure by manipulating the run_id pa
    Wysoka · 6.5 CVE-2023-22887 < 2.6.3 2.6.3
Pokaż więcej (20) Widać 40 z 65

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ę
Newsletter DockRay

Bezpieczeństwo aplikacji w Twojej skrzynce

Najważniejsze podatności, konkretne zalecenia i praktyczne wskazówki dla Twoich aplikacji. Wybierz technologie i śledź to, co ma znaczenie dla Twojego projektu.

  • Codzienne zestawienie nowych podatności, także krytycznych.
  • Powiadomienia o ważnych aktualizacjach.
  • Praktyczne porady o bezpieczeństwie i monitoringu aplikacji.

Pozostaw puste, aby otrzymywać informacje o wszystkich technologiach.

Polityka prywatności

Zapis jest bezpłatny. Wypiszesz się jednym kliknięciem w wiadomości.