Apache Airflow: information disclosure
Medium6.5CVE-2026-25219 · Published Apr 15, 2026 · updated Jul 13, 2026
The `access_key` and `connection_string` connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidently logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data. If you used Azure Service Bus connection with those values set or if you have other connections with those values storing senesitve values, you should upgrade Airflow to 3.1.8.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| apache-airflow PyPI | < 3.1.8 | 3.1.8 |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-200
- Also known as
- BIT-airflow-2026-25219, CVE-2026-25219, PYSEC-2026-2344
More Apache Airflow advisories
All Apache Airflow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Apr 18 | In case of SQL errors | High7.5 | 3.2.0 |
| Apr 18 | Apache Airflow: code execution | High7.2 | 3.2.0 |
| Apr 16 | Apache Airflow: JWT token appearing in logs | Medium7.5 | 3.2.0 |
| Apr 16 | Apache Airflow: RCE by race condition in example_xcom dag | High8.1 | 3.2.0 |
| Apr 13 | Apache Airflow: Unsafe Deserialization via Legacy Serialization Keys (__type/__var) Bypass in XCom API | High8.8 | 3.2.0 |
| Apr 13 | Apache Airflow: Secrets from Airflow config file logged in plain text in DAG run logs UI | Medium | 3.2.0 |