CyberRota Analysis
AI-GeneratedApache Airflow's Config API is vulnerable in multi-team deployments where sensitive configuration values, such as team-scoped Celery broker URLs and their credentials, are exposed in cleartext to authenticated Viewers with configuration-read access. This flaw arises from an inadequate masking mechanism that fails to normalize team-prefixed sections, allowing unauthorized visibility of sensitive data. Organizations utilizing multi-team mode in Apache Airflow should prioritize upgrading to version 3.3.1 or later to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)