Use of Incorrectly-Resolved Name or Reference Affecting apache-airflow-core package, versions [,3.3.0)
Threat Intelligence
This vulnerability is trending on Twitter; this may indicate a growing threat.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-APACHEAIRFLOWCORE-17963580
- published14 Jul 2026
- disclosed13 Jul 2026
- creditTran Hieu
Introduced: 13 Jul 2026
CVE-2026-59245 (opens in a new tab)How to fix?
Upgrade apache-airflow-core to version 3.3.0 or higher.
Overview
Affected versions of this package are vulnerable to Use of Incorrectly-Resolved Name or Reference through the resource_name() function in permissions.py and the mirrored core permissions module. An attacker can gain global read/edit access to all DAGs by creating or targeting a DAG with the dag_id DAGs and having per-DAG access_control granted on that DAG. The vulnerable resource_name() logic returned the raw dag_id when it matched a reserved resource name, so the valid DAG name DAGs collided with the global all-DAGs permission resource instead of resolving to its own DAG:DAGs resource. As a result, permissions intended for one DAG were applied to the global DAGs resource, exposing every DAG to the lower-privileged user.
Notes
- The issue affects both the FAB auth-manager permissions helper and the mirrored core permissions helper, so deployments using either copy of Airflow’s permission resolution can inherit the same resource-name collision.