CVE-2026-48891
Last modified
CVE-2026-48891 is a medium-severity vulnerability rated 4.3/10 on the CVSS scale. 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. EPSS estimates a 0.36% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Airflow | < 3.3.0 |
References
- https://github.com/apache/airflow/pull/67627Issue Tracking
- https://www.cve.org/CVERecord?id=CVE-2026-28563Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-48891?
How severe is CVE-2026-48891?
How do I fix CVE-2026-48891?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-48882Subscriber SQL Injection in WP Time Slots Booking Form <= 1.…8.5
- CVE-2026-48883Unauthenticated Broken Access Control in WPC Product Bundles…7.5
- CVE-2026-48885Unauthenticated Cross Site Scripting (XSS) in HollerBox <= 2…7.1
- CVE-2026-48886Unauthenticated SQL Injection in JS Help Desk <= 3.0.9 versi…9.3
- CVE-2026-48887Unauthenticated Broken Access Control in JS Help Desk <= 3.0…6.5
- CVE-2026-48889Subscriber Privilege Escalation in Amelia <= 2.3 versions.8.8
- CVE-2026-48892The Config API in Apache Airflow surfaced per-key secrets-ba…6.5
- CVE-2026-48895URL Redirection to Untrusted Site ('Open Redirect') vulnerab…7.2
- CVE-2026-48896Insufficient state checks lead to a vector that allows to by…7.5
- CVE-2026-48897Insufficient state checks lead to a vector that allows to by…7.5
- CVE-2026-48898An improper access check allows privilege escalation through…9.8
- CVE-2026-48899An improper access check allows privilege escalation through…9.8
Are you affected by CVE-2026-48891?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
