Iniciar sesión
Deutsch English Español Polski
Media

Apache Airflow, versions 2.7.0 and 2.7.1, is affected by a vulnerability that allows an authenticated user to retrieve sensitive configuration information when the "expose_config" option is set to "no

  • Publicada: 14.10.2023
  • Actualizado: 11.10.2026 12:19

Apache Airflow, versions 2.7.0 and 2.7.1, is affected by a vulnerability that allows an authenticated user to retrieve sensitive configuration information when the "expose_config" option is set to "non-sensitive-only". The expose_config option is False by default. It is recommended to upgrade to a version that is not affected.

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

PlataformaPaqueteVersiones vulnerablesCorregida en
Python (PyPI) apache-airflow >= 2.7.0, < 2.7.2 2.7.2

Referencias

Puntuación CVSS 4.3/10
Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Debilidad (CWE)
CWE-200
Plataforma
Python (PyPI)
Paquete
apache-airflow
Publicada
14.10.2023
Actualizado
11.10.2026 12:19

Fuentes y licencias

OSV / GitHub Advisory Database - GHSA-fpxx-xv4c-gxqp - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2023-204 - PyPA Advisory Database; 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.

Todas (158) en el archivo
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

Gravedad:
  1. Apache Airflow, versions 2.7.0 and 2.7.1, is affected by a vulnerability that allows an authenticated user to retrieve sensitive configuration information when the "expose_config" option is set to "no esta entrada
    Media · 4.3 CVE-2023-45348 >= 2.7.0, < 2.7.2 2.7.2
  2. 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
    Crítica · 9.1 CVE-2026-86473 >= 3.0.0, < 3.3.2 3.3.2
  3. 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()`
    Alta · 7.5 CVE-2026-68968 < 3.3.1 3.3.1
  4. 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
    Alta · 8.8 CVE-2026-67587 >= 3.3.0, < 3.3.1 3.3.1
  5. 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
    Alta · 7.3 CVE-2026-67260 >= 3.3.0, < 3.3.1 3.3.1
  6. 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
    Alta · 8.8 CVE-2026-58076 >= 3.3.0, < 3.3.1 3.3.1
  7. 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
    Crítica · 9.8 CVE-2026-33264 < 3.3.0 3.3.0
  8. 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
    Alta · 8.8 CVE-2026-42359 >= 3.2.0, < 3.2.2 3.2.2
  9. 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
    Alta · 7.5 CVE-2026-41084 >= 3.2.0, < 3.2.2 3.2.2
  10. 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'] }
    Crítica · 9.1 CVE-2026-42252 >= 3.0.0, < 3.2.2 3.2.2
  11. Apache Airflow: Authenticated users can bypass the `is_safe_url` check
    Alta · 7.2 CVE-2026-40961 < 3.2.2 3.2.2
  12. Apache Airflow Vulnerable to Deserialization of Untrusted Data
    Alta · 7.3 CVE-2026-45360 >= 3.2.0, < 3.2.2 3.2.2
  13. Apache Airflow allows code execution through crafted XCom payloads
    Alta · 7.2 CVE-2026-25917 < 3.2.0 3.2.0
  14. Apache Airflow: JWT token appearing in logs
    Alta · 7.5 CVE-2026-31987 >= 3.0.0, < 3.2.0 3.2.0
  15. Apache Airflow: RCE by race condition in example_xcom dag
    Alta · 8.1 CVE-2025-54550 < 3.2.0 3.2.0
  16. 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
    Alta · 8.8 CVE-2026-33858 >= 3.1.8, < 3.2.0 3.2.0
  17. Apache Airflow: JWT token still valid after logout
    Crítica · 9.1 CVE-2025-57735 >= 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,
    Alta · 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.
    Alta · 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
    Alta · 8.4 CVE-2024-56373 < 2.11.1 2.11.1
  21. Apache Airflow proxy credentials for various providers might leak in task logs
    Alta · 7.5 CVE-2025-68675 >= 3.0.0b1, < 3.1.6, < 2.11.1 3.1.6, 2.11.1
Mostrar más (20) Mostrando 21 de 66

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.

Conectar tu aplicación
Newsletter DockRay

La seguridad de tus aplicaciones en tu correo

Vulnerabilidades importantes, recomendaciones concretas y consejos prácticos para tus aplicaciones. Elige tus tecnologías y sigue lo que importa para tu proyecto.

  • Un resumen diario de nuevas vulnerabilidades, también las críticas.
  • Avisos sobre actualizaciones importantes.
  • Consejos prácticos sobre seguridad y monitorización de aplicaciones.

Déjalo vacío para recibir avisos de todas las tecnologías.

Política de privacidad

Suscripción gratuita. Date de baja con un clic en cualquier correo.