CVE-2026-28563 in Airflow
Summary
by MITRE • 03/17/2026
Apache Airflow versions 3.1.0 through 3.1.7 /ui/dependencies endpoint returns the full DAG dependency graph without filtering by authorized DAG IDs. This allows an authenticated user with only DAG Dependencies permission to enumerate DAGs they are not authorized to view.
Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 03/21/2026
The vulnerability identified as CVE-2026-28563 affects Apache Airflow versions 3.1.0 through 3.1.7 and represents a significant authorization bypass flaw that undermines the principle of least privilege in workflow management systems. This issue manifests through the /ui/dependencies endpoint which is designed to provide DAG dependency information but fails to properly validate user permissions before returning comprehensive dependency graphs. The flaw allows authenticated users who possess only the DAG Dependencies permission to access and enumerate DAGs that they should not be authorized to view, creating a reconnaissance opportunity for malicious actors seeking to understand the organization's workflow infrastructure.
The technical implementation of this vulnerability stems from inadequate access control validation within the Airflow web UI component, specifically in how the system handles requests to the dependencies endpoint. When a user makes a request to /ui/dependencies, the system should filter the returned dependency graph based on the user's authorized DAG IDs according to their assigned permissions. However, the current implementation fails to perform this critical filtering step, resulting in the exposure of complete DAG dependency information to unauthorized users. This represents a clear violation of the CWE-285 permission validation principle and demonstrates a failure in the authorization mechanism's enforcement. The vulnerability specifically targets the web UI's dependency graph rendering functionality and operates at the application layer where user permissions are managed and enforced.
The operational impact of this vulnerability extends beyond simple information disclosure, as it provides attackers with valuable reconnaissance data about the organization's Airflow deployment. An attacker with DAG Dependencies permission can now map out the entire DAG dependency structure, identify critical workflows, understand data processing relationships, and potentially discover sensitive information about business processes and data flows. This information could be leveraged to plan more sophisticated attacks targeting specific DAGs or workflows, or to understand the broader system architecture for privilege escalation attempts. The vulnerability aligns with ATT&CK technique T1069.003 for credential access and T1580 for data from cloud storage repositories, as it enables unauthorized enumeration of system resources and sensitive workflow information. Organizations using affected Airflow versions face increased risk of targeted attacks and potential data exposure through this unauthorized enumeration capability.
The recommended mitigation strategy involves upgrading to Apache Airflow version 3.1.8 or later, which includes the necessary code fixes to properly enforce authorization controls on the dependencies endpoint. This upgrade addresses the core issue by implementing proper permission filtering that ensures users can only view DAG dependencies for workflows they are authorized to access. Organizations should also conduct thorough permission reviews and audit existing user access controls to ensure that the principle of least privilege is maintained. Security teams should monitor for any unauthorized access attempts or unusual activity patterns that might indicate exploitation of this vulnerability before the upgrade is completed. Additionally, implementing network segmentation and additional monitoring controls around the Airflow UI endpoints can provide defense-in-depth measures while the upgrade process is underway. The fix implemented in version 3.1.8 follows established security best practices for access control enforcement and aligns with industry standards for maintaining proper authorization boundaries in web applications.