BIT-airflow-2026-38743
Information Exposure vulnerability in apache-airflow (PyPI)
What is BIT-airflow-2026-38743 About?
This vulnerability in Apache Airflow allows authenticated users with read access to at least one DAG to retrieve sensitive information about other DAGs. The `/ui/dags` endpoint fails to enforce per-DAG access control on embedded Human-in-the-Loop (HITL) prompts and TaskInstance records. While it requires authentication, the ease of access to broad information once authenticated makes it a notable concern.
Affected Software
Technical Details
The /ui/dags endpoint in Apache Airflow, prior to version 3.2.1, did not properly enforce per-DAG access control for embedded Human-in-the-Loop (HITL) and TaskInstance records. An authenticated Airflow user, even if only granted read access to a single DAG, could query this endpoint and retrieve HITL prompts (including their request parameters) and full TaskInstance details for DAGs that were outside their authorized scope. Since HITL prompts and TaskInstance fields often contain operator parameters and free-form context, this flaw leads to a broader visibility of sensitive DAG-run data than intended, widening the scope of information accessible to any authenticated user beyond the RBAC boundaries.
What is the Impact of BIT-airflow-2026-38743?
Successful exploitation may allow attackers to gain unauthorized access to sensitive operational data, including workflow parameters, user inputs, and internal task details from various DAGs. This could lead to disclosure of confidential information or aid in planning further attacks.
What is the Exploitability of BIT-airflow-2026-38743?
Exploitation complexity is low, as it relies on an authenticated user successfully making a request to a susceptible endpoint. Prerequisites include active authentication as an Airflow user who has at least read access to one DAG. The vulnerability requires authentication but does not require elevated privileges beyond basic read access. The attack is remote, as it targets a web UI endpoint. There are no special conditions or constraints beyond the authentication and minimal authorization. The primary risk factor is the internal information exposure within an authenticated session, where an attacker can gain broader visibility than their assigned roles intend, potentially leaking sensitive operational details.
What are the Known Public Exploits?
| PoC Author | Link | Commentary |
|---|---|---|
| No known exploits | ||
What are the Available Fixes for BIT-airflow-2026-38743?
Available Upgrade Options
- apache-airflow
- <3.2.1rc1 → Upgrade to 3.2.1rc1
Struggling with dependency upgrades?
See how Resolved Security's drop-in replacements make it simple.
Book a demoAdditional Resources
- https://lists.apache.org/thread/sk2wj0x48o8qb4p7c47gvnhjbm0mg396
- https://osv.dev/vulnerability/GHSA-p3v3-229h-mc63
- https://lists.apache.org/thread/sk2wj0x48o8qb4p7c47gvnhjbm0mg396
- http://www.openwall.com/lists/oss-security/2026/04/24/3
- https://github.com/apache/airflow/pull/64822
- https://github.com/apache/airflow/pull/64822
- https://nvd.nist.gov/vuln/detail/CVE-2026-38743
- http://www.openwall.com/lists/oss-security/2026/04/24/3
- https://github.com/apache/airflow
- https://github.com/apache/airflow/commit/fed4921098d51fd3ec17b7f5cff80f6c36fd05e2
What are Similar Vulnerabilities to BIT-airflow-2026-38743?
Similar Vulnerabilities: CVE-2023-24998 , CVE-2022-23307 , CVE-2021-44228 , CVE-2020-0081 , CVE-2023-34988
