Apache Airflow's Config API did not mask team-scoped sensitive configuration values in multi-team deployments. When an administrator has enabled multi-team mode and exposed the Config API, an authenticated Viewer holding only configuration-read access — with no prior access to the secret — could read a team-scoped Celery broker URL, including its embedded credentials, in cleartext, while the equivalent global option was correctly masked. The secrets masker matched only base section and option names and did not normalize team-prefixed sections before the sensitivity check (CWE-200). This is a distinct masker bypass from CVE-2026-48828 and CVE-2026-48892: deployments that upgraded to apache-airflow 3.3.0 to address those issues remain affected by this team-scoped variant. Users are advised to upgrade to apache-airflow 3.3.1 or later, which normalizes team-scoped sections before masking.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/70755 Issue Tracking, Patch
- https://lists.apache.org/thread/kykn94kjf0tntx4wywtvjowh5bzdgf38 Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.5 · apacheNVD modified 2026-10-23 20:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:airflow:*:*:*:*:*:*:*:*
References 4
- https://github.com/apache/airflow/pull/70755 Issue Tracking, Patch
- https://lists.apache.org/thread/kykn94kjf0tntx4wywtvjowh5bzdgf38 Mailing List, Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-48828 Not Applicable
- https://www.cve.org/CVERecord?id=CVE-2026-48892 Not Applicable