← Advisories

Apache Airflow 3.3.2 (mask_secret()) Secrets Masker Deep-Nesting Secret Leak

Medium
Advisory ID
ZSL-2026-6018
Release Date
13 October 2026
Vendor
The Apache Software Foundation - https://www.apache.org
Affected Version
3.3.2
CVE
N/A
Tested On
GNU/Linux x86_64, Python 3.10+
Summary

Apache Airflow is an open-source platform for developing, scheduling, and monitoring workflows, such as traditional time based or event-triggered batch-oriented data pipelines, machine learning, model training, and agentic or LLM-based workloads. Airflow’s extensible Python framework enables you to build workflows connecting with virtually any technology, with a growing set of providers for orchestrating AI and agentic tools alongside the rest of your pipeline. A web-based UI helps you visualize, manage, and debug your workflows. You can run Airflow in a variety of configurations - from a single process on your laptop to a distributed system capable of handling massive workloads.

Description

Apache Airflow suffers from a sensitive information disclosure vulnerability caused by an incomplete secret-masking routine. In the secrets masker, container structures are walked without a depth limit for key-name redaction, but pattern-based masking of registered secrets is applied only to string values at or below a fixed recursion depth (MAX_RECURSION_DEPTH): beyond that depth the scalar is returned as-is, before the secret-replacement step runs. As a result, a configured secret that appears as a string value nested under non-sensitive keys several container levels deep is not redacted and is emitted in clear text to task logs. An operator, or anyone with log access, can recover credentials that were expected to be masked.

Proof of Concept
Disclosure Timeline
13.08.2026Vulnerability discovered.
18.08.2026Contact with the vendor.
19.08.2026Vendor forwards details to appropriate PMC.
25.08.2026Vendor acknowledges the assessment, investigating further and asked us about release timeline. Informed that this is residual of CVE-2026-32690.
25.08.2026Replied to the vendor.
09.09.2026Vendor concluded the assessment and accepted this as a valid vulnerability.
09.09.2026Replied to the vendor.
12.10.2026Asked vendor for status update.
13.10.2026No response from the vendor.
13.10.2026Public security advisory released.
Credits
Vulnerability discovered by Gjoko Krstic
References
Changelog
13.10.2026Initial release