Anmelden
Deutsch English Español Polski
Mittel

Apache Airflow has an authorization bypass in DagRun wait endpoint

  • Veröffentlicht: 09.04.2026
  • Aktualisiert: 11.10.2026 15:17

Apache Airflow versions 3.0.0 through 3.1.8 DagRun wait endpoint returns XCom result values even to users who only have DAG Run read permissions, such as the Viewer role.This behavior conflicts with the FAB RBAC model, which treats XCom as a separate protected resource, and with the security model documentation that defines the Viewer role as read-only.

Airflow uses the FAB Auth Manager to manage access control on a per-resource basis. The Viewer role is intended to be read-only by default, and the security model documentation defines Viewer users as those who can inspect DAGs without accessing sensitive execution results.

Users are recommended to upgrade to Apache Airflow 3.2.0 which resolves this issue.

Betroffene Software

Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.

PlattformPaketAnfällige VersionenBehoben in
Python (PyPI) apache-airflow >= 3.0.0, < 3.2.0 3.2.0

Verweise

CVSS-Wert 6.5/10
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Schwäche (CWE)
CWE-668
Plattform
Python (PyPI)
Paket
apache-airflow
Veröffentlicht
09.04.2026
Aktualisiert
11.10.2026 15:17

Quellen und Lizenzen

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

OSV / GitHub Advisory Database - GHSA-r7vr-m4jw-r794 - CC BY 4.0

Schwachstellenhistorie: apache-airflow

Alle veröffentlichten Schwachstellen dieses Pakets (Python (PyPI)), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.

Alle (158) im Archiv
Einträge insgesamt
158
Erste → letzte
08.2018 09.2026
Ohne Fix
4
In Angriffen ausgenutzt
2

Verteilung nach Schweregrad

  • Kritisch 16
  • Hoch 49
  • Mittel 86
  • Niedrig 7

Veröffentlichungen pro Jahr

Schweregrad:
  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
    Kritisch · 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()`
    Hoch · 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
    Hoch · 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
    Hoch · 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
    Hoch · 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
    Kritisch · 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
    Hoch · 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
    Hoch · 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'] }
    Kritisch · 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
    Hoch · 7.2 CVE-2026-40961 < 3.2.2 3.2.2
  11. Apache Airflow Vulnerable to Deserialization of Untrusted Data
    Hoch · 7.3 CVE-2026-45360 >= 3.2.0, < 3.2.2 3.2.2
  12. Apache Airflow allows code execution through crafted XCom payloads
    Hoch · 7.2 CVE-2026-25917 < 3.2.0 3.2.0
  13. Apache Airflow: JWT token appearing in logs
    Hoch · 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
    Hoch · 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
    Hoch · 8.8 CVE-2026-33858 >= 3.1.8, < 3.2.0 3.2.0
  16. Apache Airflow: JWT token still valid after logout
    Kritisch · 9.1 CVE-2025-57735 >= 3.0.0, < 3.2.0 3.2.0
  17. Apache Airflow has an authorization bypass in DagRun wait endpoint dieser Eintrag
    Mittel · 6.5 CVE-2026-34538 >= 3.0.0, < 3.2.0 3.2.0
  18. 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,
    Hoch · 8.1 CVE-2026-30911 >= 3.1.0, < 3.1.8 3.1.8
  19. 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.
    Hoch · 7.5 CVE-2026-28779 >= 3.0.0, < 3.1.8 3.1.8
  20. Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table
    Hoch · 8.4 CVE-2024-56373 < 2.11.1 2.11.1
  21. Apache Airflow proxy credentials for various providers might leak in task logs
    Hoch · 7.5 CVE-2025-68675 >= 3.0.0b1, < 3.1.6, < 2.11.1 3.1.6, 2.11.1
  22. Apache Airflow secrets in rendered templates could contain parts of sensitive values when truncated
    Hoch · 7.5 CVE-2025-68438 >= 3.1.0, < 3.1.6 3.1.6
  23. Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context
    Kritisch · 9.8 CVE-2025-67895 < 2.0.0 2.0.0
  24. Apache Airflow: Sensitive configuration values are not masked in the logs by default
    Hoch · 7.5 CVE-2024-45784 < 2.10.3 2.10.3
  25. Apache Airflow vulnerable to Improper Encoding or Escaping of Output
    Hoch · 8.8 CVE-2024-45498 >= 2.10.0, < 2.10.1 2.10.1
  26. Apache Airflow vulnerable to Execution with Unnecessary Privileges
    Hoch · 8.8 CVE-2024-45034 < 2.10.1 2.10.1
  27. Apache Airflow has DAG Author Code Execution possibility in airflow-scheduler
    Hoch · 8.8 CVE-2024-39877 >= 2.4.0, < 2.9.3 2.9.3
  28. 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
    Hoch · 7.5 CVE-2023-50943 < 2.8.1 2.8.1
  29. 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
    Hoch · 6.5 CVE-2023-50944 < 2.8.1 2.8.1
  30. 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
    Hoch · 6.5 CVE-2023-42781 < 2.7.3 2.7.3
  31. Apache Airflow Celery provider Insertion of Sensitive Information into Log File vulnerability
    Hoch · 7.5 CVE-2023-46215 >= 1.10.0, < 2.7.0 2.7.0
  32. 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
    Hoch · 6.5 CVE-2023-40712 < 2.7.1 2.7.1
  33. 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
    Hoch · 8.1 CVE-2023-37379 < 2.7.0 2.7.0
  34. 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
    Hoch · 8.0 CVE-2023-40273 < 2.7.1rc1 2.7.1rc1
  35. apache-airflow-providers-apache-drill Improper Input Validation vulnerability
    Hoch · 7.5 CVE-2023-39553 < 2.4.3 2.4.3
  36. 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
    Hoch · 8.8 CVE-2023-39508 < 2.6.0 2.6.0
  37. 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
    Hoch · 6.5 CVE-2022-46651 < 2.6.3 2.6.3
  38. 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
    Hoch · 6.5 CVE-2023-35908 < 2.6.3 2.6.3
  39. 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
    Hoch · 6.5 CVE-2023-22888 < 2.6.3 2.6.3
  40. 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
    Hoch · 6.5 CVE-2023-36543 < 2.6.3 2.6.3
Mehr anzeigen (20) 40 von 66 angezeigt

Erkennen Sie Schwachstellen in Ihrer Anwendung

Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.

Anwendung verbinden
DockRay Newsletter

Anwendungssicherheit in Ihrem Postfach

Wichtige Schwachstellen, konkrete Empfehlungen und praktische Tipps für Ihre Anwendungen. Wählen Sie Ihre Technologien und verfolgen Sie, was für Ihr Projekt relevant ist.

  • Eine tägliche Zusammenfassung neuer Schwachstellen, auch kritischer.
  • Benachrichtigungen über wichtige Updates.
  • Praktische Tipps zur Sicherheit und Überwachung von Anwendungen.

Leer lassen, um Meldungen zu allen Technologien zu erhalten.

Datenschutzerklärung

Kostenlos anmelden. In jeder E-Mail mit einem Klick abmelden.