High [CVE-2025-66236] Apache Airflow: Secrets from Airflow config file logged in plain text in DAG run logs UI
This high-severity Apache Software Foundation advisory covers CVE-2025-66236 affecting Airflow.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
Before Airflow 3.2.0, it was unclear that secure Airflow deployments require the Deployment Manager to take appropriate actions and pay attention to security details and security model of Airflow.
Some assumptions the Deployment Manager could make were not clear or explicit enough, even though Airflow's intentions and security model of Airflow did not suggest different assumptions. The overall security model [1], workload isolation [2], and JWT authentication details [3] are now described in more detail.
Users concerned with role isolation and following the Airflow security model of Airflow are advised to upgrade to Airflow 3.2, where several security improvements have been implemented. They should also read and follow the relevant documents to make sure that their deployment is secure enough.
It also clarifies that the Deployment Manager is ultimately responsible for securing your Airflow deployment. This had also been communicated via Airflow 3.2.0 Blog announcement [4].
[3] JWT Token authentication:
Users are recommended to upgrade to version 3.2.0, which fixes this issue.
- Apache Airflow 3.0.0 before 3.2.0
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
Mitigation checklist
- Users concerned with role isolation and following the Airflow security model of Airflow are advised to upgrade to Airflow 3.2, where several security improvements have been implemented.
- This had also been communicated via Airflow 3.2.0 Blog announcement [4]. [1] Security Model: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [2] Workload isolation: https://airflow.apache.org/docs/apache-airflow/stable/security/workload.html [3] JWT Token authentication: https://airflow.apache.org/docs/apache-airflow/stable/security/jwt_token_authentication.html [4] Airflow 3.2.0 Blog announcement: https://airflow.apache.org/blog/airflow-3.2.0/ Users are recommended to upgrade to version 3.2.0, which fixes this issue.
Official advisory · high-confidence parse· fetched 1 month ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-38743Apr 24, 2026Airflow: The authenticated /ui/dags endpoint did not enforce per-DAG access control
- CVE-2026-40948Apr 18, 2026The Keycloak authentication manager in `apache-airflow-providers-keycloak` did not
- CVE-2026-32228Apr 18, 2026UI / API User with asset materialize permission could trigger dags they had no access to.
- CVE-2026-30912Apr 18, 2026Apache Airflow: In case of SQL errors, exception/stack trace of errors was exposed in API
- CVE-2026-30898Apr 18, 2026example of BashOperator in Airflow documentation suggested a way of passing dag_run.conf
- CVE-2026-25917Apr 18, 2026Apache Airflow: Dag Authors, who normally should not be able to execute code
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.