Quick answers
- Is CVE-2026-59245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59245 being exploited in the wild.
- How severe is CVE-2026-59245?
- Informational severity, with a CVSS score of 0, published 13 July 2026.
- Which products and versions are affected?
- Apache Software Foundation Airflow FAB Provider < 3.7.2.
- Is there a fix for CVE-2026-59245?
- A patch was published on 2026-07-06: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59245 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59245?
- Check whether you run Apache Software Foundation Airflow FAB Provider 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.
Technical details
A privilege escalation vulnerability exists in the Apache Airflow FAB auth manager due to a resource name collision in the `resource_name()` function. When a DAG is created with the ID `DAGs`, the auth manager fails to distinguish it from the global 'all-DAGs' permission resource. Consequently, granting a low-privileged user `access_control` permissions on a DAG named `DAGs` silently elevates their privileges to include global read/edit access across all DAGs in the environment. The fix, introduced in `apache-airflow-providers-fab` 3.7.2, removes a short-circuit logic that allowed bare reserved resource names to bypass the standard `DAG:<dag_id>` prefixing.
Affected products
- Apache Software Foundation Apache Airflow FAB provider < 3.7.2
Timeline
- 2026-06-28: disclosed: Initial pull request submitted to Apache Airflow repository
- 2026-07-06: patched: Fix merged into main branch
- 2026-07-13: advisory: CVE published by Apache Software Foundation