Apache Airflow exposes sensitive information in its log files
Medium6.5CVE-2025-27555 · Published Feb 24, 2026 · updated Sep 10, 2026
Airflow versions before 2.11.1 have a vulnerability that allows authenticated users with audit log access to see sensitive values in audit logs which they should not see. When sensitive connection parameters were set via airflow CLI, values of those variables appeared in the audit log and were stored unencrypted in the Airflow database. While this risk is limited to users with audit log access, it is recommended to upgrade to Airflow 2.11.1 or a later version, which addresses this issue. Users who previously used the CLI to set connections should manually delete entries with those connection sensitive values from the log table. This is similar but not the same issue as CVE-2024-50378
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| apache-airflow PyPI | < 2.11.1 | 2.11.1 |
Details and references
More Apache Airflow advisories
All Apache Airflow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Mar 17 | Apache Airflow: DAG authorization bypass | Medium4.3 | 3.1.8 |
| Mar 17 | Apache Airflow: Wildcard DagVersion Listing Bypasses Per‑DAG RBAC and Leaks Metadata | High7.5 | 3.1.8 |
| Feb 24 | Apache Airflow vulnerable to Code Injection in the web-server context via LogTemplate table | High8.4 | 2.11.1 |
| Feb 21 | Apache Airflow error reporting may expose full kwargs | Medium6.5 | 2.11.1+1 more |
| Feb 9 | Apache Airflow UI Exposes DAG Import Errors to Unauthorized Authenticated Users | Medium6.5 | 3.1.7 |
| Feb 9 | Apache Airflow Has an Authorization Bypass That Allows Unauthorized Task Log Access | Medium6.5 | 3.1.7 |