Apache Airflow exposes unreadable DAG identifiers in the scheduling dependencies graph (CVE-2026-48891)

Apache Airflow exposes unreadable DAG identifiers in the scheduling dependencies graph (CVE-2026-48891) | HOL Guard CVE

Why this deserves its current priority

CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps apache-airflow (pip). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
apache-airflowpip	<3.3.0	3.3.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for apache-airflow.
Review the reported fix. Update apache-airflow to 3.3.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Jul 7, 2026
Evidence: source:ghsa:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:ghsa:source_dates:source-dates:record
First seen by HOL
Jul 7, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.