CVE-2026-59245 in Apache Airflow Providers FAB
In the Apache Airflow FAB auth manager, a DAG whose `dag_id` is `DAGs` collided with the global all-DAGs permission resource name produced by `resource_name()`, so a user granted per-DAG `access_control` on that one DAG was silently granted the global all-DAGs permission (privilege escalation). The escalation triggers when a DAG named `DAGs` exists and a lower-privileged user is given per-DAG access to it, granting that user read/edit access to every DAG. Users are advised to upgrade to `apache-airflow-providers-fab` 3.7.2 or later, which disambiguates the resource-name collision.
Quick answer
Apache Software Foundation Apache Airflow Providers FAB should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- apache-airflow-providers-fab before 3.7.2
Fixed versions
- apache-airflow-providers-fab 3.7.2 or later
How to fix it
CVE-2026-59245 affects Apache Airflow Providers FAB. In simple terms, an attacker may be able to misuse the affected system if it is exposed or if a user opens unsafe input. Update to apache-airflow-providers-fab 3.7.2 or later. If you cannot update right away, limit access until the fix is installed.
- Find every place where Apache Airflow Providers FAB is installed or used.
- Check the installed version against the affected versions on this page.
- Update to apache-airflow-providers-fab 3.7.2 or later.
- If an update is not possible today, turn off the risky feature or restrict it to trusted users only.
- Review recent logs for strange access, failed logins, changed files, or unexpected admin actions.
- Rotate passwords, API keys, and tokens if you think the system may have been abused.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Apache Airflow Providers FAB now runs a fixed version or has the vendor mitigation in place.
- Test the affected feature again and make sure normal users can still work.
- Check that public or untrusted access is blocked where it should be blocked.
- Review logs again after the fix and confirm the same suspicious activity does not continue.
- Run a new Fixnx scan or your normal security check and save the result.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59245?
Apache Software Foundation Apache Airflow Providers FAB versions listed as affected should be reviewed: apache-airflow-providers-fab before 3.7.2.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.