CVE-2026-48891: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Airflow
A bug in Apache Airflow's `/ui/dependencies` scheduling graph endpoint applied the caller's readable-Dag filter to the top-level serialized Dag key but still emitted referenced Dag IDs through the `dep.source` and `dep.target` fields of trigger / sensor dependency entries. An authenticated UI user with read permission on some Dags could enumerate the identifiers of other Dags they were not authorized to read by inspecting the dependency graph for trigger / sensor references. Affects deployments that rely on per-Dag read scoping to keep Dag identifiers private across teams. This is a residual gap in the fix for CVE-2026-28563, which filtered the top-level Dag key but did not propagate the filter into the trigger / sensor dep-source / dep-target fields. Users who already upgraded for CVE-2026-28563 should additionally upgrade to `apache-airflow` 3.3.0 or later to cover the residual trigger / sensor dependency leak.
AI Analysis
Technical Summary
Apache Airflow's `/ui/dependencies` scheduling graph endpoint applies a readable-DAG filter to the top-level serialized DAG key but fails to apply the same filter to the `dep.source` and `dep.target` fields of trigger/sensor dependency entries. As a result, an authenticated UI user with read permission on some DAGs can enumerate identifiers of other DAGs they are not authorized to access by inspecting these dependency fields. This vulnerability affects deployments that rely on per-DAG read scoping to keep DAG identifiers private across teams. The issue is a residual gap from the fix for CVE-2026-28563. Users who upgraded for that fix should also upgrade to Apache Airflow 3.3.0 or later to address this leak.
Potential Impact
An authenticated user with read permission on some DAGs can gain unauthorized knowledge of other DAG identifiers that they should not have access to. This exposure of sensitive information could undermine privacy or security policies that rely on DAG identifier confidentiality across teams. There is no indication of direct code execution or data modification from this vulnerability.
Mitigation Recommendations
Upgrade Apache Airflow to version 3.3.0 or later to fully address this information exposure vulnerability. This upgrade covers the residual trigger/sensor dependency leak not fixed by the prior CVE-2026-28563 patch. No other mitigation or temporary fix is indicated.
CVE-2026-48891: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Apache Software Foundation Apache Airflow
Description
A bug in Apache Airflow's `/ui/dependencies` scheduling graph endpoint applied the caller's readable-Dag filter to the top-level serialized Dag key but still emitted referenced Dag IDs through the `dep.source` and `dep.target` fields of trigger / sensor dependency entries. An authenticated UI user with read permission on some Dags could enumerate the identifiers of other Dags they were not authorized to read by inspecting the dependency graph for trigger / sensor references. Affects deployments that rely on per-Dag read scoping to keep Dag identifiers private across teams. This is a residual gap in the fix for CVE-2026-28563, which filtered the top-level Dag key but did not propagate the filter into the trigger / sensor dep-source / dep-target fields. Users who already upgraded for CVE-2026-28563 should additionally upgrade to `apache-airflow` 3.3.0 or later to cover the residual trigger / sensor dependency leak.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Airflow's `/ui/dependencies` scheduling graph endpoint applies a readable-DAG filter to the top-level serialized DAG key but fails to apply the same filter to the `dep.source` and `dep.target` fields of trigger/sensor dependency entries. As a result, an authenticated UI user with read permission on some DAGs can enumerate identifiers of other DAGs they are not authorized to access by inspecting these dependency fields. This vulnerability affects deployments that rely on per-DAG read scoping to keep DAG identifiers private across teams. The issue is a residual gap from the fix for CVE-2026-28563. Users who upgraded for that fix should also upgrade to Apache Airflow 3.3.0 or later to address this leak.
Potential Impact
An authenticated user with read permission on some DAGs can gain unauthorized knowledge of other DAG identifiers that they should not have access to. This exposure of sensitive information could undermine privacy or security policies that rely on DAG identifier confidentiality across teams. There is no indication of direct code execution or data modification from this vulnerability.
Mitigation Recommendations
Upgrade Apache Airflow to version 3.3.0 or later to fully address this information exposure vulnerability. This upgrade covers the residual trigger/sensor dependency leak not fixed by the prior CVE-2026-28563 patch. No other mitigation or temporary fix is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-26T01:31:02.693Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4ccfd027e9c79719609a6f
Added to database: 07/07/2026, 10:07:12 UTC
Last enriched: 07/07/2026, 10:22:06 UTC
Last updated: 07/07/2026, 11:31:56 UTC
Views: 17
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.