HighGHSA-46c3-5xc5-wwhvBIT-airflow-2024-45784CVE-2024-45784PYSEC-2024-182PYSEC-2026-1112

Apache Airflow: Sensitive configuration values are not masked in the logs by default

Published 15 Nov 2024 · Updated 7 Jul 2026

Is your project on an affected airflow?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<2.10.3
Fixed in
2.10.3
Update to the fixed version for your release line, for example:pip install 'airflow>=2.10.3'

Details

Apache Airflow versions before 2.10.3 contain a vulnerability that could expose sensitive configuration variables in task logs. This vulnerability allows DAG authors to unintentionally or intentionally log sensitive configuration variables. Unauthorized users could access these logs, potentially exposing critical data that could be exploited to compromise the security of the Airflow deployment. In version 2.10.3, secrets are now masked in task logs to prevent sensitive configuration variables from being exposed in the logging output. Users should upgrade to Airflow 2.10.3 or the latest version to eliminate this vulnerability. If you suspect that DAG authors could have logged the secret values to the logs and that your logs are not additionally protected, it is also recommended that you update those secrets.

Is GHSA-46c3-5xc5-wwhv in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected airflow, and gives you the command that fixes it.

More advisories for airflow

  • MediumCVE-2019-12417Apache Airflow vulnerable to XSS and local file disclosure · 22 Nov 2019
airflow security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.