CVE-2025-66236: Apache Airflow: Secrets from Airflow config file logged in plain text in DAG run logs UI

[Rahul Vats <rahulvats () apache org>]

Severity: moderate 

Affected versions:

- Apache Airflow (apache-airflow) 3.0.0 before 3.2.0

Description:

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].

[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.

Credit:

Saurabh Banawar (finder)
Amogh Desai (remediation developer)

References:

https://github.com/apache/airflow/pull/58662
https://airflow.apache.org/
https://www.cve.org/CVERecord?id=CVE-2025-66236