Quick answers
- Is CVE-2026-111454 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111454 being exploited in the wild.
- How severe is CVE-2026-111454?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow before 3.4.0.
- Is there a fix for CVE-2026-111454?
- Yes: fixed in apache-airflow 3.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111454 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-111454?
- Check whether you run Apache Airflow at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: apache-airflow 3.4.0
Technical details
The asset API endpoints (GET /api/v2/assets, GET /api/v2/assets/{asset_id}, and the UI GET /ui/assets) returned nested references to scheduled DAGs, producing tasks, and consuming tasks without filtering them against the user's readable DAGs. An authenticated user with asset read access could enumerate workflow IDs they lacked direct read permissions for by examining the asset API responses. The fix applies the existing ReadableDagsFilterDep filter to narrow these nested references to only those DAGs the user can read.
Affected products
- Apache Airflow before 3.4.0