Sensitive Information Exposure in Apache Airflow

apache-airflow Updated 02 Oct 2025

Summary

14/10/2023
Yes i
Moderate
6.5

CVE-2023-42663: Apache Airflow vulnerable to sensitive information exposure. Affects apache-airflow versions < 2.7.2. Fixed in 2.7.2. How to fix ↓

Also tracked for

The same CVE-2023-42663 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Apache Airflow is an open-source platform used for programmatically authoring, scheduling, and monitoring workflows. It allows users to define tasks and their dependencies as Directed Acyclic Graphs (DAGs) and execute them on a distributed infrastructure. Apache Airflow is widely adopted for its flexibility and scalability in managing complex workflows.

Vulnerability Detail

Apache Airflow versions before 2.7.2 are vulnerable to sensitive information exposure. This vulnerability allows an authorized user with access to read specific DAGs to also read information about task instances in other DAGs. This means that an attacker with access to one DAG can potentially gain unauthorized access to sensitive information from other DAGs. The impact of this vulnerability depends on the sensitivity of the information stored in the affected DAGs.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.7.2

This is the first release that contains the fix.

pip install --upgrade "apache-airflow==2.7.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to upgrade to the latest version of Apache Airflow as soon as possible.

Conclusion

Apache Airflow versions before 2.7.2 are vulnerable to sensitive information exposure. To mitigate this vulnerability, it is crucial to upgrade to the latest version of Apache Airflow. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for apache-airflow →

Share this vulnerability

FAQ

Apache Airflow is an open-source platform used for programmatically authoring, scheduling, and monitoring workflows.

The impact of this vulnerability depends on the sensitivity of the information stored in the affected DAGs. An attacker with access to one DAG can potentially gain unauthorized access to sensitive information from other DAGs.

To fix this vulnerability, upgrade to Apache Airflow version 2.7.2 or newer.

There is no known workaround for this vulnerability. It is recommended to upgrade to the latest version of Apache Airflow.

You can find more information about this vulnerability in the Apache Airflow advisory: [link to advisory]

Related vulnerabilities

Recent vulnerabilities recorded for apache-airflow.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.7.2

This is the first release that contains the fix.

pip install --upgrade "apache-airflow==2.7.2"

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback