CVE-2026-28563 is a security vulnerability identified in Apache Airflow versions 3.1.0 through 3.1.7 that involves incorrect permission assignment (CWE-732) on the /ui/dependencies endpoint. This endpoint returns the full DAG dependency graph without filtering based on the authenticated user's authorized DAG IDs. As a result, any user with the DAG Dependencies permission can enumerate all DAGs within the Airflow environment, including those they are not authorized to view. This unauthorized enumeration can lead to exposure of sensitive workflow structures, potentially revealing business logic, operational processes, or other confidential information embedded within DAGs. The vulnerability does not allow modification or execution of unauthorized DAGs but compromises confidentiality by leaking metadata about workflows. The flaw arises because the endpoint fails to enforce proper access control checks on the DAG dependency data it returns. Apache Airflow 3.1.8 and later versions have addressed this issue by implementing appropriate filtering to restrict DAG visibility according to user permissions. There are no known exploits in the wild at this time, but the vulnerability is publicly disclosed and should be considered a risk for organizations using affected Airflow versions. The vulnerability requires authentication and the DAG Dependencies permission, which limits exposure to internal or trusted users with some level of access. However, insider threats or compromised accounts could exploit this to gain unauthorized insight into workflow configurations. The absence of a CVSS score necessitates an assessment based on impact and exploitability factors.

The primary impact of CVE-2026-28563 is unauthorized information disclosure, affecting the confidentiality of workflow metadata within Apache Airflow environments. Organizations relying on Airflow for orchestrating critical business processes may inadvertently expose sensitive DAG structures to users who should not have visibility, potentially revealing proprietary operational details or security-sensitive workflow dependencies. This could facilitate further attacks by providing adversaries or malicious insiders with intelligence about internal processes. While the vulnerability does not allow direct modification or execution of unauthorized workflows, the exposure of DAG dependencies can undermine trust in the system's access controls and may violate compliance requirements related to data confidentiality. The scope is limited to authenticated users with DAG Dependencies permission, reducing the risk of external exploitation but increasing concerns about insider threats. The availability and integrity of Airflow workflows are not directly impacted by this vulnerability. However, the reputational damage and potential regulatory consequences from unauthorized data exposure could be significant for organizations in regulated industries or those with sensitive operational workflows.

To mitigate CVE-2026-28563, organizations should upgrade Apache Airflow to version 3.1.8 or later, where the vulnerability has been fixed by enforcing proper access control filtering on the /ui/dependencies endpoint. Until upgrading is possible, administrators should review and restrict the assignment of the DAG Dependencies permission to only trusted users who require it for their role, minimizing the number of users who can exploit this flaw. Implement network segmentation and access controls to limit access to the Airflow UI and API endpoints to authorized personnel only. Monitor logs and audit access to the /ui/dependencies endpoint for unusual or unauthorized enumeration activities. Employ strong authentication mechanisms and consider multi-factor authentication to reduce the risk of compromised credentials being used to exploit this vulnerability. Additionally, conduct regular security reviews of Airflow permissions and configurations to ensure least privilege principles are enforced. If feasible, disable or restrict access to the /ui/dependencies endpoint temporarily as a stopgap measure. Finally, maintain awareness of updates from the Apache Software Foundation and apply security patches promptly.